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
Certain DDL operations work correctly when performed on freshly created database, and fail after backup/restore cycle.
The reason for failure is that system generators used to produce field names do not preserve their values during backup/restore cycle.
After backup/restore generated field names are no longer unique. Scripts to reproduce are attached.
Test case. Run messup.cmd to see the failure:
Statement failed, SQLSTATE = 42000
unsuccessful metadata update
-cannot delete
-DOMAIN RDB$1
-there are 1 dependencies
After line 17 in file messup2.sql
If you remove backup/restore step from the script it will finish without errors
Submitted by: @samofatov
Attachments:
messup1.sql
messup2.sql
messup.cmd
Votes: 3
Certain DDL operations work correctly when performed on freshly created database, and fail after backup/restore cycle.
The reason for failure is that system generators used to produce field names do not preserve their values during backup/restore cycle.
After backup/restore generated field names are no longer unique. Scripts to reproduce are attached.
Commits: a01baa2 136463b 843dfc2 07c631f
The text was updated successfully, but these errors were encountered: