Bug #35092 entering text in SQL Query Area in overwrite mode produces strange results
Submitted: 6 Mar 2008 0:09 Modified: 4 Feb 2009 9:50
Reporter: Ron Gommers Email Updates:
Status: Closed Impact on me:
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.2.12 through 1.2.16 OS:Microsoft Windows
Assigned to: Mike Lischke
Tags: insert, overwrite
Triage: D3 (Medium)

[6 Mar 2008 0:09] Ron Gommers
When typing text in the "SQL Query Area" in "overwrite" mode 
only on the first character of a line, existing text is 
overwritten as expected.
When "over"-typing a character at pos 2 in the line, the character is entered, but the next character has disappeared

line: "12345"        after typeing an "X" at pos 2: "1X45"
line: "1234567890"   after typeing an "X" at pos 3: "12X67890"

looks like a simple logic error to me!
something to do for Mike ?


How to repeat:
in the SQL Query Area type "1234567890"
Now press the "insert" key to go to overwrite mode
Position the cursor at the "5" 
Type a "5" 
output : "123450"

Only when on the first character this seems to work all right.

Something for Mike ?
[6 Mar 2008 5:29] Valeriy Kravchuk
Thank you for a bug report.
[4 Feb 2009 1:44] Ron Gommers
It's been almost a year now, and nothing happened...
Imagine typeing a lot of neat SQL statements, then, out of habit, you press the insert key to start overwriting a small piece of text. boom.
End of exercise, you can start all over again (and no ability to ctrl-z back to where you were)

I understand this is not a major MySql problem, but I use the Query Browser frequently and I assume I'm not the only one. iT's really annoying to have to start over again every time I assume the insert key to work like it is supposed to...

Can you give me a timeframe...


[4 Feb 2009 9:50] Mike Lischke
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at