Subject | Re: [ib-support] Multy database ? |
---|---|
Author | Fabricio Araujo |
Post date | 2001-03-05T22:49:22Z |
On Mon, 05 Mar 2001 11:10:07 -0500, Ann W. Harrison wrote:
client must know where the DB is.
If we have aliasing, and make the alterations on our "beloved"
optimizer and query processor, cross-DB is possible.
Actually (via SQL - not QLI, GDML, etc) we not even have a
way to NAME this cross-db attach. SELECT blablabla from "server:/ibpath/ibdb.gdb". TABLE
is a real pain even thinking about it...
[]s Fabricio
Systems Developer
>At 06:25 AM 3/5/2001 -0300, Fabricio Araujo wrote:Oh... I forgot this "little" detail, after years lurking these lists... ;-)))
>
>>A transaction can be opened and oper with 2 DB connections, but only on
>>client side.
>>But SQL only understands commands regarding current database.
>
>Actually, an InterBase multi-database transaction is server side,
>for what little that's worth.
>You are quite correct that ourIB/Firebird or whatever it calls ;-)) is made in a way the
>SQL implementation gives no access to multi-database operations
>and that is a problem.
client must know where the DB is.
If we have aliasing, and make the alterations on our "beloved"
optimizer and query processor, cross-DB is possible.
Actually (via SQL - not QLI, GDML, etc) we not even have a
way to NAME this cross-db attach. SELECT blablabla from "server:/ibpath/ibdb.gdb". TABLE
is a real pain even thinking about it...
[]s Fabricio
Systems Developer