Claudio Valderrama C. wrote:

>>
>> Speaking of which, is qli still fully usable with recent
>> Firebird versions?
>
> Not in v3, but we still don't release v2.5 final and in v2.5 it's fully
> functional.
> :-)
>

I can say for sure that in 2.1.2 (see below for full details)
the error handling has degenerated to
Expected <whatever> found <whatever>
where <whatever> could be anything, but whatever it expected is
what it found.



I miss the report writer, the ability to specify column headers,
output formats, define relation like relation (coming to a SQL
near you -not that it works any more ... recursion (now in SQL,
but really ugly compared to the GDML version) - having a husband
with a dark mustache, and some other parts of my youth. But I
don't miss them enough to make them work again (or to make him
dye his mustache).


QLI> define relation tt1 like t2
** QLI error: expected column definition clause, encountered
"column definition clause" **


Cheers,

Ann


QLI> ready foo.fdb
QLI> show version
QLI, version "WI-V2.1.2.18118 Firebird 2.1"
Version(s) for database "foo.fdb"
Firebird/x86/Windows NT (access method),
version "WI-V2.1.2.18118 Firebird 2.1"
Firebird/x86/Windows NT (remote server),
version "WI-V2.1.2.18118 Firebird 2.1/XNet (HOTSPUR)/P11"
Firebird/x86/Windows NT (remote interface),
version "WI-V2.1.2.18118 Firebird 2.1/XNet (HOTSPUR)/P11"
on disk structure version 11.1

QLI>