| Bug #49182 | "MYSQL Workbench" can`t synchronize table with ENUM column type | ||
|---|---|---|---|
| Submitted: | 28 Nov 2009 23:51 | Modified: | 14 Jun 2010 13:44 |
| Reporter: | Oleh Herych | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | 5.1.18 OSS | OS: | Windows (SP3) |
| Assigned to: | Alexander Musienko | CPU Architecture: | Any |
| Tags: | Data Type, database, workbench | ||
[14 Jun 2010 10:59]
Johannes Taxacher
fix confirmed in repository
[14 Jun 2010 13:44]
Tony Bedford
An entry has been added to the 5.2.23 changelog:
When synchronizing with a live database, MySQL Workbench did not interpret whitespace in ENUMs correctly. For example, ENUM('image', 'video', 'swf') was seen as different from ENUM('image','video','swf'), causing the live server and model to appear unsynchronized.
Description: "MYSQL Workbench" doesn't see the difference between "ENUM('image', 'video', 'swf')" and "ENUM('image','video','swf')" (without whitespaces) How to repeat: 1. Create column in table with type "ENUM('image', 'video', 'swf')" in MYSQL Workbench 2. Synchronize with the database 3. Synchronize again. Application generate SQL to change this column. But i didn't change it. Suggested fix: I think that MySQL database optimized type of column and deleted whitespaces. MYSQL Workbench gets scheme and tries to compare current column type with his one. It uses default string binary compare function.