Subject | Re: [Firebird-Architect] RFC: Cross database queries |
---|---|
Author | Alex Peshkov |
Post date | 2007-08-01T13:08:23Z |
On Wednesday 01 August 2007 16:38, Roman Rokytskyy wrote:
for them.
PS.Don't want to say that I have plans to do it myself.
which should me merge version. I suppose we may prepare to introduce new
versions of SQLDA, SPB, may be even DPB/TPB in some version in the future -
anyway sooner or later we need long identifiers.
> >> If former - we don't need PROVIDER clause then - it should be part ofWhy not? If we need to talk to external datasources, this is the best place
> >> Firebird. BTW, we don't have clause to register provider :)
> >
> > Because we don't need it. If provider will be regular Vulcan-style
> > provider it will be registered in appropriate config file
>
> Do you want to implement ODBC, JDBC or other adapters as providers in
> Vulcan architecture?
for them.
PS.Don't want to say that I have plans to do it myself.
> > I not agree with you here. As for me cross-database queries must beIdeally both should be taken into an account:)
> > as easy from end-user POV as usual queries
>
> Who is end-user in our case? Software developer or user of the software?
> > This is the only positive i see in extending CREATE TABLE :)Let's do not forget that this feature is not for 2.1 and even not for 3.0,
>
> Well... if you have a better idea to handle long tables names from other
> database engines in XSQLVAR without changing the XSQLDA version or API -
> I'm all ears :)
which should me merge version. I suppose we may prepare to introduce new
versions of SQLDA, SPB, may be even DPB/TPB in some version in the future -
anyway sooner or later we need long identifiers.