At 11:11 AM 14-03-02 +0000, you wrote:

>Helen (or another list moderator that it's not asleep now):
>
>I don't want to cross post between different newsgroups (you already spank
>me once), but I think that C. Valderrama explanation "why he changed
>Firebird" should be post here.
>
>My first impression to this problem was that "Firebird team should keep
>backward compatibility", no matter if IBO is doing some now-SQL standard.
>
>But looking at Claudio's explanation I'm going to think twice.

Artur, if you are talking about the discussion on firebird-devel, please
re-read Claudio's message carefully. As I understand it, he is agreeing to
revisit the fix he did that produced this unforeseen side-effect for
IBO. Correctly, I believe.

For now, we have a problem with thousands of IBO sites running software
that depends on the capability of InterBase to accept a table-identified
column-list in an INSERT statement. It is correct that the argument should
continue to be made with Claudio so that he sees this is NOT like the
ambiguous join syntax restriction that was introduced earlier. That
actually FIXED something that was broken.

Claudio is currently arguing against merely reversing the fix that he did -
he is talking of modifying the code to re-enable an identified column list
while continuing to disallow a statement that breaks the engine, vix.
INSERT INTO ATABLE(ATABLE.*)
VALUES (...)

So let's go in there and encourage Claudio to do that, for the sake of all
our customer sites who want to switch to Firebird.


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at
www.ibobjects.com