Bug #22949 No formating done upon edit, of sql statemant for defining a 'View'
Submitted: 3 Oct 2006 16:47 Modified: 4 Oct 2006 9:21
Reporter: Heinz Schweitzer (Gold Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.4 RC OS:Windows (XP)
Assigned to: CPU Architecture:Any

[3 Oct 2006 16:47] Heinz Schweitzer 
Description:
No formating done upon edit, of sql statemant for defining a 'View'

**********************************************
systeminformation
**********************************************
MySQL Administrator 1.2.4 RC (German)
MySQL-Server-Information
--------------------------------------------------------------------------------
Mit MySQL-Serverinstanz verbunden
  Benutzername:            root
  Hostname:                localhost
  Port:                    3306
--------------------------------------------------------------------------------
Serverinformation
  MySQL-Version:           MySQL 5.0.18-nt via TCP/IP
  Netzwerkname:            localhost
  IP:                      127.0.0.1
--------------------------------------------------------------------------------
Clientinformation
  Version:                 MySQL Client Version 5.0.11
  Netzwerkname:            hgs
  IP:                      192.168.2.5
  Betriebssystem:          Windows XP
  Hardware:                Intel(R) Pentium(R) 4 CPU 2.00GHz, 504 MB RAM

How to repeat:
Open the Mysql Administrator (German localized)
select Kataloge-->mysql
In the right pane activate the 'View' tab

In there just create a simple vire if there is none (like
CREATE OR REPLACE VIEW `mysql`.`aaa` AS SELECT * from db
Save the view)

Open the view with the edit view button.
Window pops up with just one very long line like in screen
shot v1.

Suggested fix:
Please add some meaningfull line breaks.
[3 Oct 2006 16:48] Heinz Schweitzer 
v1

Attachment: v1.png (image/png, text), 9.97 KiB.
[4 Oct 2006 9:21] Sveta Smirnova 
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicates Bug #20354