|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is duplicated by:
|
|
CORE-2070
Wrong evaluation of domain's check constraint for sp input parameter
|
|
|
|
|
Relate
|
|
|
|
This issue is related to:
|
|
|
|
|
|
|
|
|
| Planning Status: |
Unspecified
|
|
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.
|
|
Description
|
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. |
Show » |
committed 1 file to 'Firebird' - 12/Aug/08 07:22 AM
Fixed CORE-2039: Domain-level CHECK constraints wrongly process NULL values.
|
|
|
committed 1 file to 'Firebird' on branch 'B2_1_Release' - 12/Aug/08 07:26 AM
Fixed CORE-2039: Domain-level CHECK constraints wrongly process NULL values.
|
|
|
|
Bug
Domain-level CHECK constraints wrongly process NULL values
