Bug #13240 | Clearing a fields should result in NULL value | ||
---|---|---|---|
Submitted: | 15 Sep 2005 22:52 | Modified: | 16 Sep 2005 4:17 |
Reporter: | Frank Maas (Basic Quality Contributor) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.1.14 | OS: | Windows (Windows 2000) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[15 Sep 2005 22:52]
Frank Maas
[16 Sep 2005 4:17]
MySQL Verification Team
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: That will create more problem when the column in the table creation was defined as NOT NULL also as the empty "" one.
[16 Sep 2005 7:20]
Frank Maas
Thanks for your reply. I can see your point in creating more problems with my solution. But in all honesty: I cannot find anything in the documentation that describes how to insert a NULL value. I even downloaded the PDF version and searched for 'NULL': nothing relevant found. Perhaps I am just stupid (and Dutch), but since I did not find it I took it for (a) a bug in the documentation, (b) a bug in QB (handling empty fields), or (c) a feature request.