Obviously, there are lots of differences in the functionality between DBISQL and the deprecated dbisqlc tools, e.g. DBISQL's editable query result window, import/export facilities, editing, source code integration, different input/output formats, locking of result sets, and much more. - And surely there are not so obvious ones, too.
But what are the differences when it comes to query processing, i.e. is the assumption correct that both tools should handle the same query identically (well, except for locking issues)?
I do raise this question as there seem to be some syntax variants that are handled differently by both tools, e.g. EXCEPT statements enclosed in parantheses.
Are there some general differences in that respect, or are they just unwanted and only based on the frozen dbisqlc parsing?
(If the answer is version specific, I would like to get an answer for v12.)
asked 10 Apr '11, 15:40
In short, I don't think anyone really knows the answer to that question. Dbisql is under active development and I'm sure that team knows it inside out. Dbisqlc has been out of active development for so long that nobody knows it inside out any more. I can imagine that dbisql was originally written to closely mimic dbisqlc but it may have diverged since then. Nobody has maintained an active comparison of the two applications.
Here are a few general things that come to mind:
For the most part, query processing is done on the engine side so differences in that regard should be rare.
If you have a specific difference you want to more about, I can look into it.