> Imagine that we need to add a WHERE clause to activate a filter:
>
> SELECT T1.COL, T2.COL
> FROM TAB1 T1, TAB2 T2
> WHERE T1.COL = 0
>
> But since our API doesn't report the relation alias, the library may do:
>
> SELECT T1.COL, T2.COL
> FROM TAB1 T1, TAB2 T2
> WHERE COL = 0
>
> Obviously, this is practically useless due to the possible ambiguity. So
> libraries do:
>
> SELECT T1.COL, T2.COL
> FROM TAB1 T1, TAB2 T2
> WHERE TAB1.COL = 0
>
> Which worked quite well. But we have two problems here:
>
> 1) it doesn't work with two references to a single relation (unexpected
> result is produced)
> 2) this query is no longer valid in FB 2.0 (SQL-99 rejects it as well)
>
> Shortly said, FB 2.0 breaks a significant subset of the FIBPlus features.
> IBO is also expected to be affected. Cannot say for others.

Just to confirm, IBO is also affected.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com