The ability to deal directly with two databases is an ability of the
QLI application -- and has nothing to do with the GDML language (the
older InterBase language).

There's really nothing to prevent ISQL / WISQL, or anyone else's SQL
front-end from adding the ability to the level that QLI had it. (add
some syntax to indicate which database each substatement refers to --
and a front end SQL parser).

Now, what would be really interesting, is to add the ability to the
engine to query a different database.

Dave




-----Original Message-----
From: Doug Chamberlin [mailto:dchamberlin@...]
Sent: Saturday, January 15, 2000 2:38 PM
To: IBDI@onelist.com
Subject: Re: [IBDI] QLI and ancient IB language


From: Doug Chamberlin <dchamberlin@...>

At 1/15/2000 04:27 PM (Saturday), Rob Schuff wrote:

>My personal bias is to keep InterBase as standards compliant as

possible

>unless there is some way cool thing that couldn't be done without

QLI.

>Frankly, I'm not do not know what QLI capabilities are. Perhaps Ann

could

>enlighten us poor souls.

The one SQL extension I would like to see carried from QLI to the
Interbase
SQLdialect is the ability to deal directly with two databases in one
SQL
statement. For example, to be able to insert records from a table in
one
database by selecting them from another.


--------------------------- ONElist
Sponsor ----------------------------

Hey Freelancers: Find your next project through JobSwarm!
You can even make money in your sleep by referring friends.
<a href=" http://clickme.onelist.com/ad/jobswarm1 ">Click Here</a>

----------------------------------------------------------------------
--

Community email addresses:
Post message: IBDI@onelist.com
Subscribe: IBDI-subscribe@onelist.com
Unsubscribe: IBDI-unsubscribe@onelist.com
List owner: IBDI-owner@onelist.com

Shortcut URL to this page:
http://www.onelist.com/community/IBDI



[This message contained attachments]