Null values in NOT NULL column [CORE2352] #2775
Comments
|
Commented by: @asfernandes We can do nothing without a reproducible test case. |
|
Commented by: Miroslav Djorov (miro) If I remember right in Firebird 2.X when there are existing connections to the database and someone make a change in a stored procedure, the existing connections continue to work with the older version of the changed stored procedure until all connections to the database are closed. After that the new connections work with the actual version of the stored procedure. Because when I made the changes in the database there were some active connections. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Miroslav Djorov (miro)
In existing table I've added a new column : SMALLINT DEFAULT 0 NOT NULL. It must have values 0,1 and 2.
All existing records got 0s in this column.
New records for this table are inserted from two stored procedures(values 0 and 2) and from my Delphi application ( value 1).
I have changed stored procedures' inserts to add values in the new column. The values are hard coded - 0 and 2, they are not from variables. Now only the records inserted from the Delphi application have values - 1.
All records from the stored procedures are with NULL.
The text was updated successfully, but these errors were encountered: