New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unrestorable backup [CORE1748] #2173
Comments
Modified by: Igor Lobov (ivl)Attachment: test.sql [ 10773 ] |
Commented by: @cincuranet IMO it's not bug, it's by design. You have to add column and if it's NOT NULL, you have to fill it with some data yourself. |
Commented by: Igor Lobov (ivl) Maybe it is not a bug, but it is potential hole in Firebird backup system. |
Commented by: @dyemanov You *can* restore such a backup (at least since v2.0) using a "-no_validity" switch. |
Commented by: Csaba Lassán (cslassan) Dear All, in my opinion this serious bug is related more to the server core itself than the backup utility, because no one shall add "not null" columns to populated tables. If there is a way to do it, that means one can make a self-conflicting data definition! |
Commented by: @dyemanov While this can be treated as a bug, this is actually the intentional behavior inherited from the very old InterBase versions. |
Commented by: Csaba Lassán (cslassan) Dear Dmitry, may Codd bless You :D |
Modified by: @dyemanovFix Version: 3.0 Alpha 1 [ 10331 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Igor Lobov (ivl)
Is duplicated by CORE2458
Relate to CORE2696
Is related to QA540
Attachments:
test.sql
I have table with NOT NULL fields with records.
If some count of NOT NULL fields are clear I can create backup file without any errors, but can not restore it.
I attached simple script of example database.
Commits: 218f419
The text was updated successfully, but these errors were encountered: