"Josipovic, Nikica" wrote:

>
> No problems to come at all as long as the SQL is proper done.
> Every problem resulting from Ambiguity checks have their cause not in the
> SQL-Engine, but in the user who did create the SQL.
> You wouldn't have been able to create ambigous SQL in DB/2, Sybase and
> MS-SQL. Interbase did it, although the SQL-Standard does not offer this
> possibility, and the Firebird Team simply removed a "bug" in terms of
> Standard SQL.
>

In the TCS suite there is even documentation for one of the tests noting that
ambiguous field names are illegal against most db servers - and the note is
dated around 1994!

Paul
--

Paul Reeves
http://www.ibphoenix.com
taking InterBase further