Everyone is grumping about the ANSI join syntax, and I grump about obscure
abortions like the Oracle outer join syntax. But the solution is one we
are going to implement some time soon, which is to write a SQL parser that
creates a parse tree, lets us modify the tree as requires (more
selections, grouping etc), and then writes the tree out in the SQL target
dialect.
Using this strategy you can have any sort of primary syntax that you like
and works, and then translate into the backend syntax quickly and easily.
We did intend to do the ANSI join stuff as the primary as it is, at least,
specific and unambigious to beginners, and then translate to fix what ever
platform dependancies cropped up. But there is nothing to stop you writing
all your SQL in syntax A and translating is to any other syntax as long as
they have all the features required.
Cheers, Max.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
