MySQL Bugs: #53873: An INSERT value input

Bug #53873	An INSERT value input
Submitted:	21 May 2010 6:37	Modified:	21 Jun 2010 13:48
Reporter:	Adrian Sta„czak	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.2	OS:	Windows (Win 7)
Assigned to:		CPU Architecture:	Any

Description:
A message box appeared informing me that there was a bug (accessing protected memory) while writing down a value into a field in a Tables Inserts card. Value was being entered through Workbench's API and not being confirmed when the problem occured. However the entry did change as it was supposed to.
Field type was VARCHAR, and the input text length did not exceed the maximum character limit.

How to repeat:
Input text into a VARCHAR field through Inserts Card and press Enter. Happens only every once in a while. Other conditions are hard to specify.

Suggested fix:
See if the bug indicator feature is working properly itself, because I'm not shure that something really did go wrong.

It is of not big need but a maximum VARCHAR (and other value) cap for character numbers might be useful for people with less familiarity. I think the discribed error was due to too high maximum character limit set.

What exact version of MySQL Workbench, 5.2.x, do you use? Please, send CREATE TABLE statement for the table in question also.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".