Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | Tools - ER Modeler |
| Version | 17.0 |
I have an ER model with MySql 5.6 as the target.
If I create a column with a data type of int, it defaults the precision to 15. If I remove the 15 (ie no precision set), save & close and reopen it adds a precision of 15 back in. It should leave my precision (or lack there of) alone :)
Second, this default precision of 15 is used for all int types-- tinyint, smallint, mediumint, int, and bigint. Which is pretty big for a tinyint and is actually too small for a bigint.
And finally, why 15 in the first place? If it was an int, the max actual precision is 11 for a signed field and 10 for an unsigned field.
http://dev.mysql.com/doc/refman/5.7/en/numeric-type-attributes.html
The default for the precision option is set to default of 15. This option was attached to all the data types that have a precision property. The integer types precision property is not a true precision property but instead tells mysql how many characters to return from a stored value for display purposes. I have created a new precision option type for the integer types that will have no default. This should never be set in the ERM unless the user wishes to limit the return char count. This will affect all mysql versions ER Models.
Code changes have been made so that the default value for the precision property of integer types will now be empty for mysql ERM. This is not the case for the CREATE GUI's in data studio, where the precision is set to the max char length of the integer type.
Committed revision: 49419
Code changes have been made so that the default value for the precision property of integer types will now be empty for mysql ERM. This is not the case for the CREATE GUI's in data studio, where the precision is set to the max char length of the integer type.
Committed revision: 49419
Thanks Ivan!
Thanks Ivan!
Issue #14393 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v17.0.3-33 |
| No time estimate |
The default for the precision option is set to default of 15. This option was attached to all the data types that have a precision property. The integer types precision property is not a true precision property but instead tells mysql how many characters to return from a stored value for display purposes. I have created a new precision option type for the integer types that will have no default. This should never be set in the ERM unless the user wishes to limit the return char count. This will affect all mysql versions ER Models.