Bug #47258 | Forware engineer changes BOOLEAN columns as TINYINT | ||
---|---|---|---|
Submitted: | 10 Sep 2009 18:43 | Modified: | 11 Oct 2009 18:25 |
Reporter: | Daniel GArnier | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.1.16 | OS: | Windows (XP) |
Assigned to: | CPU Architecture: | Any | |
Tags: | boolean, changes, datatype, Tinyint, workbench |
[10 Sep 2009 18:43]
Daniel GArnier
[10 Sep 2009 18:44]
Daniel GArnier
This is the slq generate boy my phpmyadmin
Attachment: test_script.sql (application/octet-stream, text), 1.68 KiB.
[10 Sep 2009 18:45]
Daniel GArnier
This is the test model i create to repeat the bug
Attachment: test_database.mwb (application/octet-stream, text), 5.45 KiB.
[10 Sep 2009 18:49]
Daniel GArnier
Also, when I surpass 75 tables in the model, the workbench become very unstable and too slow to refresh the draw.
[10 Sep 2009 18:54]
Peter Laursen
There is no BOOL/BOOLEAN data types (used for storage) in MySQL. http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html says "BOOL, BOOLEAN: These types are synonyms for TINYINT(1)." .. so a client may specify 'BOOLEAN' but the server translates to TINYINT(1) Peter“(not a MySQL person)
[11 Sep 2009 4:05]
Valeriy Kravchuk
As for instability and slow redraw, please, check WB 5.1.18. It may have some improvements. I agree with Peter - as soon as SQL is generated for MySQL server this is not a bug actually.
[11 Sep 2009 17:30]
Daniel GArnier
Thanks to all for your quick response. I continue my projecto without problems about using the tinyints. I will try the new version of WB. Thanks again
[11 Sep 2009 18:25]
Valeriy Kravchuk
Please, inform about any similar problems in 5.1.18.
[11 Oct 2009 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".