Subject | Re: [firebird-support] using multiple databases |
---|---|
Author | Daniel Rail |
Post date | 2005-02-25T14:00:33Z |
Hi,
At February 25, 2005, 04:53, Tim wrote:
didn't use use DB aliases, like Sybase does, it probably would've been
hard to implement. For this to be properly implemented, it's a
possibility that you would have to only use aliases, and that the
concept of namespace be implemented in Firebird. And, that when
compiling a trigger or a stored procedure, and even preparing a query,
Firebird will have to be aware of other databases, which at the moment
is not the case.
Because of the time that this might take to implement, if someone is
desperate enough to have this feature and willing to help pay for the
development to have it sooner, I'm sure it can be arranged via the
Firebird Foundation.
My guess it will be easier to implement once Firebird 3.0 is released,
especially if it will have the provider concept that Vulcan will be
introducing. Then it will be to introduce the namespace concept, and
that the only requirement will be to only use DB aliases to be able to
use the cross-database functionality.
But, this is probably only the tip of the iceberg in regards to what
has to be done to implement the cross-database feature.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)
At February 25, 2005, 04:53, Tim wrote:
> None of this is meant to be a rant in any way, or a criticism of either FBI also agree that this feature will be useful. Because Firebird
> or any person on the list.
didn't use use DB aliases, like Sybase does, it probably would've been
hard to implement. For this to be properly implemented, it's a
possibility that you would have to only use aliases, and that the
concept of namespace be implemented in Firebird. And, that when
compiling a trigger or a stored procedure, and even preparing a query,
Firebird will have to be aware of other databases, which at the moment
is not the case.
Because of the time that this might take to implement, if someone is
desperate enough to have this feature and willing to help pay for the
development to have it sooner, I'm sure it can be arranged via the
Firebird Foundation.
My guess it will be easier to implement once Firebird 3.0 is released,
especially if it will have the provider concept that Vulcan will be
introducing. Then it will be to introduce the namespace concept, and
that the only requirement will be to only use DB aliases to be able to
use the cross-database functionality.
But, this is probably only the tip of the iceberg in regards to what
has to be done to implement the cross-database feature.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)