>>Mark D. Stock wrote
>>>>So what is ISQL. ( I did a search on the IBM web site and clicked on ISQL and it took me to the
>>>>4GL page :-( )
>>>Oh, now that would confuse.
>>>ISQL was the product that gave birth to DBaccess. Think of what DBaccess
>>>gives you, then add forms generation (ever heard of perform?),
>>Yes, and used it, that was standard in SE 4.X
> More like SE was standard with ISQL. The early versions of the tools,
> ISQL, I4GL, etc. came bundled with "the" engine, which was SE. Then they
> split them into separate products, so that you could buy the engine
> separately, although it wasn't much good without ISQL, as there was no
> Although I thought that SE was already a separate product at version 4.x.
First came ISQL 1.10; then came ISQL 2.00 and I4GL 1.00; then ISQL
2.10 and I4GL 1.10; then ISQL/I4GL 2.10.03/1.10.03 - and a new product
called Informix-Turbo; and then came ISQL 4.00, I4GL 4.00, SE 4.00 and
OnLine 4.00. Incidentally, the ESQL/C version numbers were one ahead
of ISQL (2.10, 3.00, 3.10, 3.10.03, etc, until 4.00).
The .03 products might have been renumbered as version 3 except that
Informix had another product - Informix 3.30 - which was only off the
market for a couple of years at the time. That had the formbuild,
perform, aceprep and acego programs to which Jack alluded, and a
program called - drum roll, please - informix! And one called informer.
ISQL 1.10 supported SQL without nulls. The ACE program accessed the
database through a separate program, sqlexec, but Perform needed to do
things which were not available via sqlexec, so it included the engine
logic in it, and was a SUID root, SGID informix executable as a result.
ISQL 2.00 and I4GL 1.00 added nulls and three-valued logic (ugh!).
When you bought either product, you got the sqlexec executable with
it. I4GL 1.10 had a number of useful new features, including windows.
I forget whether scroll cursors were added in 1.10 or 1.10.03, but
when they were added, ISQL became a sane citizen and Perform used the
database server instead of being a server.
At the time the .03 releases were made, it became possible to nominate
which database engine to use via the SQLEXEC environment variable.
This was because there were plans afoot to add a super-dupe high
performance alternative to sqlexec - sqlturbo which was the most
important part of the Informix-Turbo product. This was another reason
why Perform needed to use the database server, of course. But when
you bought ISQL or I4GL, you still got sqlexec with the product.
With the great version number unification scheme, everything jumped to
version 4.00. The Turbo product was renamed OnLine (but the engine
executable remained sqlturbo, and the utility names started tb), and
SE was completely separate. When you bought ISQL or I4GL, you also
had to buy (or ensure you had access to) a database server. And I-Net
and I-Star were available for distributed access to databases.
Version numbers remained unified at release 4.10. I4GL and ISQL did
not jump to 5.00 in synchrony with OnLine and SE and ESQL/C because
the team was hard at work on 4GL++, which eventually became NewEra.
Jonathan Leffler #include <disclaimer.h>
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/