Subject Update against uncommitted DDL misbehaves
Author davidalbiston

I posted this as a problem with Flame Robin but Milan Babuskov has
pointed out that the problem is with Firebird and can be reproduced
with ISQL.

Using FB 1.5.2 on XP, I added a new column to a table. Without
committing the DDL statement, I went on to update the new column with
a value. The value was posted to the new column and ALSO to the first
column in the table.

Is this a known problem or should I register it as a new issue?