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
Previosly when updating a table with a script Firebird admitted a to add a not NULL field without a Default value. I understand the reasons why it changed but what about trying to add a NOT NULL Foreign Key to a populated table? Of course it is impossible because you cannot define a Default Value or the data would be inconsistent or you have to use a "non visible row" to accomplish it. This "improvement" is a huge problem for many of us.
I use extensive use of scripts to update my customers and this change ban me from Firebird 3 becasue I cannot find a way to workaround this.
Thanks in advance,
The text was updated successfully, but these errors were encountered:
First create the new field without NOT NULL. Then set its value to a non null value. After switch on the NOT NULL on the field, for example ALTER TABLE TABLE1 ALTER FIELD1 SET NOT NULL;
Please read "Manage Nullability in Domains and Columns" section in the release notes of 3.0.x.
Submitted by: Alfonso Presa (foncci)
Previosly when updating a table with a script Firebird admitted a to add a not NULL field without a Default value. I understand the reasons why it changed but what about trying to add a NOT NULL Foreign Key to a populated table? Of course it is impossible because you cannot define a Default Value or the data would be inconsistent or you have to use a "non visible row" to accomplish it. This "improvement" is a huge problem for many of us.
I use extensive use of scripts to update my customers and this change ban me from Firebird 3 becasue I cannot find a way to workaround this.
Thanks in advance,
The text was updated successfully, but these errors were encountered: