> > anthony.bydeveldt wrote:
> > > Just 1 more question guys!
> > >
> > > Can anyone tell me which SQL standard the ambiguity rule relating
> to table aliases was introduced?
> > >
> > > I understand that the rule wasn't enforced until firebird v2, but I
> wanted to know which SQL standard that was introduced into.
> > >
> > > I am planning on getting the developer to change the software based
> on it not being SQL standard compliant, as we will be using this
> software into the foreseeable future and we don't want to get stuck on
> a 2004 version database server.
> >

I'm not even sure that this is an explicit part of the SQL standards. There
are many things which are left to implementation and not explicitly required
in the standard.
The standard says: "avoid ambiguity"
FB 1.5 was allowing some level of ambiguity even though developers were
quite able to avoid it.
FB 2 was a move to prevent sloppy programming and force the developer to
make an unambiguous decision about which field he wanted.

I think the only argument you have is that regardless of the server version,
his SQL is/was sloppy and ambiguous.
They will argue that under 1.5 it returned the desired result and therefore
is not a bug.

Sorry
Alan