[#CORE-3461] DDL operations fail after backup/restore

Firebird Core

DDL operations fail after backup/restore

Created: 04/May/11 11:28 PM Updated: 23/Apr/13 12:03 PM

Component/s:

None

Affects Version/s:

3.0 Initial, 2.0.6, 2.5.0, 2.1.4

Fix Version/s:

2.5.1, 2.1.5, 3.0 Alpha 1

Time Tracking:

Not Specified

File Attachments:

messup.cmd (0.1 kB)
2.

messup1.sql (0.3 kB)
3.

messup2.sql (0.3 kB)

Planning Status:

Unspecified

Description

« Hide

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.

All

Comments

Work Log

Change History

Version Control

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Nickolay Samofatov added a comment - 04/May/11 11:30 PM

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

[ Permalink | « Hide ]

Alexander Peshkov added a comment - 01/Jun/11 09:37 AM

Existing solution can't be backported directly to B2_0.