accepts invalid dates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
Critical
|
Jay Pipes |
Bug Description
from strict.test:
CREATE TABLE t1 (col1 date);
INSERT INTO t1 VALUES(
INSERT INTO t1 VALUES(
# All test cases expected to fail should return
# SQLSTATE 22007 <invalid date value>
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
--error 1292
INSERT INTO t1 VALUES(
# Standard says we should return SQLSTATE 22018
--error 1292
INSERT INTO t1 VALUES ('59');
broken.strict [ fail ]
drizzletest: At line 18: query 'INSERT INTO t1 VALUES(
Changed in drizzle: | |
status: | Fix Committed → Fix Released |
looks like 0th month or 0th day is the problem (we succeed when should fail)