Commented by: Sean Leyne (seanleyne)

More details are required.

Please describe the exact commands executed, their sequence and whether transactions are committed in between each statement...

Commented by: Sean Leyne (seanleyne)

Since no additional details have been provided, after waiting several weeks, to allow for this issue to be reproduced. This issue/case must be closed.

Commented by: @pavel-zotov

> whether transactions are committed in between each statement

I think this can be reproduced like this:

set autoddl off;
create table test(id int primary key);
drop table test;
create table test(id int primary key, x int);

Output on WI-V2.5.5.26914 and WI-V3.0.0.31940:

Statement failed, SQLSTATE = 42000
unsuccessful metadata update
-too few key columns found for index RDB$PRIMARY1 (incorrect column name?)

Commented by: Sean Leyne (seanleyne)

I am not so sure if your example is what the OP meant. I read "whether transactions are committed in between each statement" to mean that they were committing in between each DDL statement. Such as:

create table test(id int primary key);
commit;
drop table test;
commit;
create table test(id int primary key, x int);
commit;

but without details from OP, I don't think we should speculate.

Regarding your example, I do not think it is valid. If a developer chooses to use "set autoddl off" (default is "on") then they become responsible for applying/committing DDL in appropriate fashion. No error occurs "set autoddl off" is omitted and/or if "commits" are present, so at best I believe this issue could be closed as "Won't Fix".