You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nobody would normally attempt such silly FK relationship, but the engine should handle it gracefully:
create table t(a int primary key);
alter table mon$statements add constraint z foreign key(mon$statement_id) references t(a);
Produces in the debug build:
Statement failed, SQLSTATE = 08006
connection lost to database
Statement failed, SQLSTATE = 08006
Error writing data to the connection.
Submitted by: Claudio Valderrama C. (robocop)
Nobody would normally attempt such silly FK relationship, but the engine should handle it gracefully:
create table t(a int primary key);
alter table mon$statements add constraint z foreign key(mon$statement_id) references t(a);
Produces in the debug build:
Statement failed, SQLSTATE = 08006
connection lost to database
Statement failed, SQLSTATE = 08006
Error writing data to the connection.
The release build says:
Statement failed, SQLSTATE = 42000
unsuccessful metadata update
-persistent table "MON$STATEMENTS" cannot reference persistent table "T"
that's a sign it's not handling the case entirely well, since it identifies MON$STATEMENTS as persistent.
The text was updated successfully, but these errors were encountered: