Bug #17509 | No warning for exceeded key length limits | ||
---|---|---|---|
Submitted: | 17 Feb 2006 8:49 | Modified: | 21 Mar 2018 14:04 |
Reporter: | Kristian Koehntopp | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S4 (Feature request) |
Version: | 1.0.23 | OS: | Windows (Windows) |
Assigned to: | CPU Architecture: | Any |
[17 Feb 2006 8:49]
Kristian Koehntopp
[17 Feb 2006 8:55]
Kristian Koehntopp
Wrong versions (use MTK versions, not MySQL versions involved)
[18 Mar 2009 11:19]
Susanne Ebrecht
Many thanks for pointing this out. But I would say it is a bug and not a feature request. Verified as described by using actual version.
[21 Mar 2018 14:04]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 8.0.11 release, and here's the changelog entry: When out-of-range index, unique index, or primary key values were define in the source, no warning was provided to indicate that the code produced could not be executed by the MySQL server. Thank you for the bug report.