Timeline for MySQL IS NULL / IS NOT NULL Misbehaving?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2016 at 15:40 | comment | added | sming | FYI ToadSQL shows 0000-00-00 00:00:00 as {null}, further muddying the waters! What a nightmare. FTR we don't have an index on our problem column. This is on 5.6.15-log. | |
| Feb 19, 2012 at 2:01 | comment | added | ypercubeᵀᴹ | @ErikE: That, sometimes, is not a choice. And you'll always find reasons to pick anotehr DBMS, whatever one you are working with. | |
| Feb 19, 2012 at 1:58 | comment | added | ErikE | @yper or a reason to pick a different DBMS... | |
| Feb 17, 2012 at 12:21 | comment | added | user1213259 | I have updated the original post to show the current values in estimated_date column. It does not have 0000-00-00 or empty strings "". | |
| Feb 16, 2012 at 20:57 | comment | added | ypercubeᵀᴹ |
The bug appears when the DATE or DATETIME is defined as NOT NULL. In the question here, the column is defined as nullable. This bug however, is another reason to run MySQL in strict mode only.
|
|
| Feb 16, 2012 at 16:01 | history | edited | araqnid | CC BY-SA 3.0 |
added 189 characters in body
|
| Feb 16, 2012 at 15:20 | history | answered | araqnid | CC BY-SA 3.0 |