Bug #53066 | Character in Bigint field creates crash | ||
---|---|---|---|
Submitted: | 22 Apr 2010 14:20 | Modified: | 10 May 2010 13:40 |
Reporter: | Johan Ohlin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.19 OSS Beta Rev 5680 | OS: | Windows (Win7, XP) |
Assigned to: | Sergei Tkachenko | CPU Architecture: | Any |
Tags: | BIGINT, character, crash, EER Diagram, inserts |
[22 Apr 2010 14:20]
Johan Ohlin
[22 Apr 2010 14:57]
Valeriy Kravchuk
Thank you for the problem report. Please, check with a newer version, 5.2.19, and inform about the results.
[22 Apr 2010 15:45]
Johan Ohlin
Just tested with version 5.2.19 OSS Beta Rev 5680 and the problem remains.
[22 Apr 2010 15:58]
MySQL Verification Team
I couldn't repeat with a table built on my own. Please provide a model file project which causes the bahavior reported on your side?. Thanks in advance.
[22 Apr 2010 15:59]
Valeriy Kravchuk
I do not get any crash on Mac OS X. So, this looks like Windows-specific problem.
[22 Apr 2010 16:35]
Johan Ohlin
I created a new model file and had the same problem there so I don't think it's specific to the file I attached. The problem is probably not related to BIGINT because I had the same with an INT field.
[22 Apr 2010 16:36]
Johan Ohlin
An example model file
Attachment: Database model bug 53066.mwb (application/x-zip-compressed, text), 9.26 KiB.
[22 Apr 2010 16:36]
Johan Ohlin
Screen dump
Attachment: screen dump bug 53066.jpg (image/pjpeg, text), 188.88 KiB.
[23 Apr 2010 11:23]
Valeriy Kravchuk
Verified just as described with the last model uploaded on 32-bit Windows XP.
[28 Apr 2010 13:39]
Alfredo Kojima
Windows specific, happens whenever you type non-numeric garbage in a numeric field.
[5 May 2010 20:52]
Johannes Taxacher
fix confirmed in repository
[10 May 2010 13:40]
Tony Bedford
An entry has been added to the 5.2.21 changelog: In the Inserts tab of the Table Editor, if characters were inadvertently typed into an integer column, MySQL Workbench crashed when a new column was selected.