""Ann W. Harrison"" <aharrison@...> wrote in message
news:5.1.0.14.2.20011210094750.02363330@......

> At 09:04 PM 12/7/2001 -0400, Claudio Valderrama C. wrote:
>
> >Roger: the problem is not the optimizer, but the DSQL layer.
>
> Err, not entirely. When the engine parses and compiles the
> blr that DSQL generates, it does the same sort of thing.
> Regards,

The engine didn't detect those ambiguities before I wrote the convoluted
code in the DSQL layer. The cause was that the DSQL layer picked the first
field that matched and qualified it with the table found. So really whether
the engine detects at lower levels is irrelevant from DSQL perspective,
since the DSQL layer made each query appear as it was fully qualified. Kinda
fooling the core in behalf of the user.

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing