I was trying to avoid both since the SELECT statement is not fixed.
Time to time, users want different information.
Thanks,
Andre
On 21-Nov-08, at 12:59 PM, Peter Brawley wrote:
> Andre Matos wrote:
>
> >Today I have 5, but tomorrow I can have 50 and I don't want to
> forget any database.
>
> Do it in an app language or as a PREPARED statement in an sproc.
>
> PB
>
> ---
>
> Andre Matos wrote:
>> Hello,
>>
>> Let's suppose I have 5 database: db1, db2, db3, db4, and db5. They
>> all have the same structure but different data.
>>
>> I would like perform this select
>>
>> SELECT TaskDoneOn, TaskDoneBy
>> FROM {database}
>> WHERE TaskDoneOn IS NOT NULL
>>
>> and collect the data from all 5 database. However, I would like to
>> avoid doing something like this:
>>
>> SELECT TaskDoneOn, TaskDoneBy
>> FROM db1
>> WHERE TaskDoneOn IS NOT NULL
>> UNION
>> SELECT TaskDoneOn, TaskDoneBy
>> FROM db2
>> WHERE TaskDoneOn IS NOT NULL
>> UNION
>> SELECT TaskDoneOn, TaskDoneBy
>> FROM db3
>> WHERE TaskDoneOn IS NOT NULL
>> UNION
>> SELECT TaskDoneOn, TaskDoneBy
>> FROM db4
>> WHERE TaskDoneOn IS NOT NULL
>> UNION
>> SELECT TaskDoneOn, TaskDoneBy
>> FROM db5
>> WHERE TaskDoneOn IS NOT NULL
>>
>>
>> Today I have 5, but tomorrow I can have 50 and I don't want to
>> forget any database.
>>
>> Thanks for any help.
>>
>> Andre
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> Internal Virus Database is out of date.
>> Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus
>> Database: 270.9.0/1777 - Release Date: 11/9/2008 9:53 AM
>>
>>
--
Dr. André Matos
andrematos@stripped
