Cross database joins
Bart Pietercil
bart.pietercil at gmail.com
Wed Apr 4 12:50:20 CDT 2007
OK Thanks Ruslan,
we will take the route that the software queries the database it is
pointed to and will create the tables that are not yet defined
Bart
On 4-apr-07, at 20:44, Ruslan Zasukhin wrote:
> On 4/4/07 12:11 PM, "Bart Pietercil" <bart.pietercil at gmail.com> wrote:
>
>> Hi List,
>>
>> Is it possible to do cross database joins ?
>>
>> If in one database I have a table that I would like to use in some
>> other databases, can I do this ?
>>
>> This is the model we are thinking about
>>
>> DB1
>> users table
>>
>> DB2
>> students table
>> coaches table
>>
>> DB3
>> coaches table
>> coachees table
>>
>> .....
>>
>> All refer to the same users table
>>
>> The idea is that our product(s) should be able to run by itself
>> (product x = db1 + db2, product y = DB1 + DB3, product z = db1 +db2 +
>> db3)
>> This approach would be more modular than building complete databases
>> drom scratch for the different products
>>
>>
>> My hope is that qualified table names would work like this:
>>
>> SELECT db1.users.* from db1.users,db2.coaches WHERE
>> db2.coaches.user_ptr = xxx
>
> To be able do this we need YET implement this feature of "attached"
> tables.
>
> And as far as we see, in this case you will be able use only PK+FK,
> but not ObjectPtrs and BinaryLinks.
>
>
> --
> Best regards,
>
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc
>
> Valentina - Joining Worlds of Information
> http://www.paradigmasoft.com
>
> [I feel the need: the need for speed]
>
>
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina
More information about the Valentina
mailing list