| Subject | Re: QLI and ancient IB language |
|---|---|
| Author | Robert Love |
| Post date | 2000-01-16T15:15:57Z |
InterBase started development before SQL was a standard. I am
not sure of the time frame but I believe SQL was not even a
language let alone a standard at the time IB was started.
InterBase internally uses a language called BLR. When you
issuse a SQL statement, or create a Trigger/Stored Procedure. It
is converted to BLR before the Engine will do anything with it.
QLI I believe works much in the same way. I have heard QLI has
features that are better / Non existant in SQL. One feature it has
is to connect to multiple databases and work against both at the
same time.
Due to the nature by which this occurs. There are API calls out
there that will allow you to send BLR directly to the InterBase
engine. So in a sense you have 3 different lanaguages you can
talk to InterBase with, and if you built a converter that would
convert Lanaguage "X" to BLR you could have several numbers of
languages.
I agree with your statement that the SQL should remain as
standard as possible. However, I do have some confusion, on the
SQL standard. InterBase supports UDF does the sql standard
support them? One common request is to make several of these
functions standard within InterBase. Which I dont' have a problem
with. However is that in the SQL standard?
Robert Love
To: <IBDI@onelist.com>
Date sent: Sat, 15 Jan 2000 13:27:46 -0800
From: "Rob Schuff" <robertsc@...>
Send reply to: IBDI@onelist.com
Subject: Re: [IBDI] QLI and ancient IB language
Who am I?
SLCDUG President - http://www.slcdug.org
Delphi-Jedi FAQ, API Tips & Trick Coordinator
http://www.delphi-jedi.org
not sure of the time frame but I believe SQL was not even a
language let alone a standard at the time IB was started.
InterBase internally uses a language called BLR. When you
issuse a SQL statement, or create a Trigger/Stored Procedure. It
is converted to BLR before the Engine will do anything with it.
QLI I believe works much in the same way. I have heard QLI has
features that are better / Non existant in SQL. One feature it has
is to connect to multiple databases and work against both at the
same time.
Due to the nature by which this occurs. There are API calls out
there that will allow you to send BLR directly to the InterBase
engine. So in a sense you have 3 different lanaguages you can
talk to InterBase with, and if you built a converter that would
convert Lanaguage "X" to BLR you could have several numbers of
languages.
I agree with your statement that the SQL should remain as
standard as possible. However, I do have some confusion, on the
SQL standard. InterBase supports UDF does the sql standard
support them? One common request is to make several of these
functions standard within InterBase. Which I dont' have a problem
with. However is that in the SQL standard?
Robert Love
To: <IBDI@onelist.com>
Date sent: Sat, 15 Jan 2000 13:27:46 -0800
From: "Rob Schuff" <robertsc@...>
Send reply to: IBDI@onelist.com
Subject: Re: [IBDI] QLI and ancient IB language
> My personal bias is to keep InterBase as standards compliant as possibleRobert Love - rlove@...
> 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.
>
> rob
Who am I?
SLCDUG President - http://www.slcdug.org
Delphi-Jedi FAQ, API Tips & Trick Coordinator
http://www.delphi-jedi.org