Bug #14978 | Displays "empty string" as column-default even if no default is assigned | ||
---|---|---|---|
Submitted: | 16 Nov 2005 12:23 | Modified: | 4 Aug 2006 17:13 |
Reporter: | Bernhard Geyer | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.1.5 | OS: | Windows (XP SP2) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
Tags: | Object Editors |
[16 Nov 2005 12:23]
Bernhard Geyer
[16 Nov 2005 15:09]
MySQL Verification Team
Could you please provide more information. You see the 'empty string' when MA -> Edit Table Data opens Query browser?
[16 Nov 2005 15:17]
Bernhard Geyer
Shows that Column "Not_Null" has a default-Value "empty string"
Attachment: EmptyString_NotNull.PNG (image/png, text), 6.19 KiB.
[16 Nov 2005 15:19]
Bernhard Geyer
No, I see this in the "Edit Table"-Menu-Entry -> MySQL Table Editor See also attached Bug-File "EmptyString_NotNull.PNG"
[16 Nov 2005 15:29]
MySQL Verification Team
Is very hard to say you if this is an actually bug, or just the object is ready for you to edit a default value when double clicking. Let then our GUI team give you a better explanation for.
[16 Nov 2005 15:36]
Bernhard Geyer
I think it is a bug because if you look to the "Null_OK" field in the Table Editor. It shows a "NULL"-Icon to make visible that there is no default value (not "empty string").
[5 Jun 2006 16:41]
Lawrence Holtsclaw
I've noticed the same behavior. This could be related to another problem which I've not seen before (and not reported since I'm not sure how to classify it). Namely, using "SHOW FIELDS FROM table" returns an empty string for the default value when the column is NOT NULL. The value returned from the INFORMATION SCHEMA, however, is correct (null). Due to a bug in the MySQL client (which shows the empty string as NULL), you can only verify this by using the client library.
[4 Aug 2006 17:13]
Michael G. Zinner
I have fixed several issues with the default values. Strings have to be quoted from now on to distinguish them from empty strings ''. This should also address this bug.