Andrei,

> This is all good and makes sense, but it basically means (despite all
> claims) that Firebird is not 100% compatible with Interbase 6 and
> earlier versions since ambiguous queries like the one above have
> always worked in IB.

Actually, v1.0 testing showed that incorrect/inconsistent results could
be produced by an ambigous query.

> Also the fact that the error message is so
> obscure makes me think that this functionality was turned off by
> mistake rather than intentionally.

No, it was an intentional decision which was widely discussed at the
time.

> In any case, my project has
> thousands of queries like the one above and this little thing will
> basically prevent me from migrating to Firebird. Too bad...

In dialect 1, ambiguity issues are reported/treated as warnings. In
dialect 3, they are treated as errors.

While, I don't like the idea of 'losing' a potential Firebird
user/developer, the fact that some of your queries are ambiguous is
something that should be fixed in the long run anyways.


--
Sean Leyne

- FirebirdSQL Foundation, Sponsor - Silver Level
- FirebirdSQL Foundation, Member
- FirebirdSQL Project Admin (one of many)
http://www.FirebirdSQL.org