Subject Firebird v1.0 Final and the result set with a newly created column?!?!?
Author Thomas Steinmaurer
Hi all,

I don't know if this was discussed in the past or there already
exists an bug tracking entry at Sourceforge.

I've some strange things happening here when executing
SELECT * FROM MYTABLE after adding a new VARCHAR(40) column.

Using Firebird v1.0 Final and the isql command line utility.

Having a table like:

RECREATE TABLE MYTABLE (
ID T_ID ,
NAME T_LASTNAME ,
PRIMARY KEY (ID)
);

Starting isql and connecting to the database. The first statement
I execute is SET AUTODDL OFF;

Now lets create a new column called UPPER_NAME with
ALTER TABLE MYTABLE ADD UPPER_NAME VARCHAR(40);

Doing a SELECT * FROM MYTABLE gives a weird result set.

ID NAME UPPER_NAME
1001 Thomas 1001 <------

Damn, the primary key column value is shown for the column UPPER_NAME?!?
The same when I do a COMMIT after the ALTER TABLE statement.

Doing the SELECT * FROM MYTABLE from another connection, the result set
is correct (UPPER_NAME is NULL), so it seems that there is only something
wrong within the current connection context.

Can somebody confirm this?

Regards,
Thomas Steinmaurer
http://www.iblogmanager.com