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
Domain-level CHECK constraints wrongly process NULL values [CORE2039] #2476
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovsummary: Domain-level CHECK constraints wrongly processes NULL values => Domain-level CHECK constraints wrongly process NULL values |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Beta 1 [ 10251 ] Fix Version: 2.1.2 [ 10270 ] |
Modified by: @pmakowski |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @dyemanov
Is duplicated by CORE2070
Is related to QA223
Test case:
CREATE DOMAIN D_DATE AS DATE
CHECK (VALUE BETWEEN DATE '01.01.1900' AND DATE '01.01.2050');
CREATE PROCEDURE TMP (PDATE D_DATE)
AS BEGIN END;
COMMIT;
EXECUTE PROCEDURE TMP (NULL);
/* ERROR:
The insert failed because a column definition includes validation constraints.
validation error for variable PDATE, value "1858-11-17".
At procedure 'TMP'.
*/
As we can see, the NULL value is treated as a zero-valued date by the check constraint.
Commits: 832d9c9 585d8a3
The text was updated successfully, but these errors were encountered: