> >The only problem i currently can see is what field would have the

precedence

> >in this query :
> >
> >SELECT
> > F1 AS F2
> >FROM
> > TableX
> >WHERE
> > F2 = 1
> >
> >Where TableX has F1 and F2 as fields, should it use TableX.F1 or

TableX.F2

> >in the WHERE clause? May be a stupid example, but you can imagine...
> >
> >
> An interesting philosophical question. It could be left undefined,
> defined in one of at least three ways, or an explicit error. I favor
> the first because the second encourages doing bonehead things and the
> third strikes me as unnecessarily nasty.

Actually, I disagree. IMO, it should raise an error so that it shows
the user that there is a field "F2" in the table. That way, "undefined"
behaviour can be avoided.


With regards,

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