Bug #57865 | Datatype "DOUBLE(M,D)" will be switched into "DOUBLE" WITHOUT arguments | ||
---|---|---|---|
Submitted: | 30 Oct 2010 21:34 | Modified: | 13 Dec 2010 11:31 |
Reporter: | Tobias Suckow | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 5.2.29 CE | OS: | Windows (Windows 7 Pro) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
Tags: | Data Type, double |
[30 Oct 2010 21:34]
Tobias Suckow
[4 Nov 2010 11:37]
Johannes Taxacher
also applies to FLOAT
[10 Nov 2010 19:37]
Alfredo Kojima
Fixed. You can fix in your version by editing mysql_rdbms_info.xml and making the following changes: @@ -1394,7 +1394,7 @@ </value> <link type="object" key="group">com.mysql.rdbms.common.typegroup.numeric</link> <value type="string" key="name">FLOAT</value> - <value type="int" key="numericPrecision">0</value> + <value type="int" key="numericPrecision">53</value> <value type="int" key="numericPrecisionRadix">0</value> <value type="int" key="numericScale">30</value> <value type="int" key="parameterFormatType">6</value> @@ -1413,7 +1413,7 @@ </value> <link type="object" key="group">com.mysql.rdbms.common.typegroup.numeric</link> <value type="string" key="name">DOUBLE</value> - <value type="int" key="numericPrecision">0</value> + <value type="int" key="numericPrecision">53</value> <value type="int" key="numericPrecisionRadix">0</value> <value type="int" key="numericScale">30</value> <value type="int" key="parameterFormatType">5</value>
[8 Dec 2010 20:21]
Johannes Taxacher
fix confirmed in repository
[13 Dec 2010 11:31]
Tony Bedford
An entry has been added to the 5.2.31 changelog: When setting the data type of a column to DOUBLE with precision specified, the data type reverted to DOUBLE without the desired precision specifiers. This happened in both the Table Editor and the SQL Editor.