Lucas Franzen wrote:

>
> Until now it was legal to have statements like:
>
> INSERT INTO MYTABLE ( MYTABLE.MY_ID, MYTABLE.MY_INTEGER )
> VALUES ( 1, 2 );
>
> Now this won't work unless I omit the MYTABLE in front of the
> fieldnames.
>
> Unfortunately the table name is added automatically by (for example)
> IBO...
>

Unfortunate is a delicate way of putting it. The above did work in RC2
and doesn't appear to work now.

Unfortunate is also the term I would use to describe the fact that our
tests missed this. They do plenty of inserts into tables. But none of
the insert statements qualify the column names.

I don't know what the SQL standard says on this subject, but as you can
only insert into a single table at a time there is no danger of
ambiguity, so the qualification of each column is redundant. But that
doesn't help much if you have a truckload of code that has broken.


Paul
--

Paul Reeves
http://www.ibphoenix.com
taking InterBase further