Bug #47100 | Insert values for datatype BIT are dropped | ||
---|---|---|---|
Submitted: | 3 Sep 2009 14:32 | Modified: | 4 Nov 2009 17:40 |
Reporter: | Leif Inge Sandberg | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.2a alpha | OS: | Windows |
Assigned to: | Sergei Tkachenko | CPU Architecture: | Any |
Tags: | regression |
[3 Sep 2009 14:32]
Leif Inge Sandberg
[3 Sep 2009 14:40]
Leif Inge Sandberg
I changed the BIT column to TINYINT and opened the Insert tab. Then I found values there; 0, 1, and 2.69044e-282. It seems like Workbench does save something that can neither be shown nor saved to the export script? My workaround is to get rid of any BIT columns altogether. It's also recommended here (a bit old, though): http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/
[4 Sep 2009 6:10]
Valeriy Kravchuk
Thank you for the bug report. Verified just as described.
[3 Nov 2009 19:13]
Johannes Taxacher
this has been fixed in repository. fix will be included in 5.2.7
[4 Nov 2009 17:40]
Tony Bedford
An entry was added to the 5.2.7 changelog: In the Inserts tab of the Table Editor, values entered for a BIT column were not saved. If values were entered and then the changes applied, the values in the BIT column disappeared.