Bug #9095 Hitting ESC key clears SQL
Submitted: 10 Mar 2005 15:51 Modified: 11 Apr 2005 10:03
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.6 OS:Windows (Windows XP [Version 5.1.2600])
Assigned to: CPU Architecture:Any

[10 Mar 2005 15:51] [ name withheld ] 
Description:
When editing SQL in the "SQL Query Area", if you hit the Escape key, the SQL is cleared.

Pressing Ctrl-Z to undo does *not* undo this.

What can I say, I'm a Vim user.  I get irked about this in Excel/OOo Spreadsheet too.  (Though, in the spreadsheets, you've only lost a cell's worth of editing).

If you've edited a sufficiently long piece of SQL (i.e., anything non-trivial), this is infuriating: this isn't just cosmetic, it's a good reason not to use Query Browser to develop queries.

How to repeat:
* Type a really long, complex, important SQL query in the Query Browser.
* Press Escape.
* Watch in horror as QB clears the screen.
* Press Ctrl-Z
* Watch in bafflement as QB fails to undo :-(

Suggested fix:
unknown
[11 Mar 2005 9:50] Aleksey Kishkin 
Hi!
It's not a bug but rather feature request. Could you please change severity to 'feature request' and status to 'open'?
[11 Mar 2005 10:03] [ name withheld ] 
If Ctrl-Z allowed me to undo it, then it would be a feature request.
The fact that it is blown away without mercy means it's a bug.

You cannot develop SQL in Query Browser.  (and that sounds like a bug ;->)

I've discussed with some colleagues who agree, but please let me know what you think!
[11 Mar 2005 20:56] Emanuele Dolis 
Well, 
can we make this matter of the ESC key customizable?
For instance I find it a very user-friendly feature to clear the SQL windows (from long, complex queries) when I've got to past a query written in a script whose result I'd like to preview.
You know how it is..... ;) anyone has its habits!

Bye
Emanuele
[14 Apr 2005 23:00] Bugs System 
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".