MySQL Bugs: #14760: "Edit view" brings up definition in one long line -- hard to comprehend

Bug #14760	"Edit view" brings up definition in one long line -- hard to comprehend
Submitted:	8 Nov 2005 16:25	Modified:	11 Mar 2009 11:35
Reporter:	Gisbert Selke (Basic Quality Contributor)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S4 (Feature request)
Version:	1.1.17	OS:	Windows (Win XP)
Assigned to:		CPU Architecture:	Any

Description:
It would be nice if "edit view" wouldn't bring up the definitions
in just one humongous line but rather inserted some line breaks (even
if only semi-intelligently). 
In addition, even after editing in line breaks, these seem to be gone the next time one edits the view. This makes editing needlessly tedious. (Editing stored procedures/functions fortunately doesn't have this problem.)

Actually, this may not be a problem of QueryBrowser but of the way views are stored internally in the server. (Are line breaks etc. removed?)

How to repeat:
(1) Enter some query, execute, hit "Create View" button, store under some name. Highlight view, right click, "edit". I expect to see the view definition in some legible format, but I get one long line.
(2) Edit in some sensible line breaks. Hit "Execute" in order to store changed definition in server. Close edit pane. Reopen in "edit" mode again, and the original hard-to-read layout will be there again.

Thank you for a reasonable feature request. Now the results of SHOW CREATE VIEW from server are just used.

This bug seems to get reported multiple times but never adressed. I can't see (from my somewhat simplistic POV) why views should be treated any differently from stored procedures, and then editing of these is fine.

Any update on whether this will happen anytime soon? It's one of the Query Browser's major shortfalls for serious work. Most report development happens at the view level; having to manually parse the view code over and over every time you work on a view (or just want to see what it does) is time consuming and irritating. More importantly, there's no way to store and retrieve comments with the code - which is rather helpful when creating views to be utilized by others, or wanting to document the reasoning behind the code.

The way this works for stored procedures is flawless, btw.

Hi there. Ok, you've got me... how on earth are you all editing Views?? It's impossible to work with a view that has say, 50 lines of code, if it all appears on one line. Isn't this a routine task for all mysql developers, it certainly is for me. I must be missing something.. this bug, which must be trivial to fix, was logged in 2006, a last update in Jan 2007, and now it's 2008. Will someone enlighten me. I've tried using phpMyAdmin, but it's dreadful and you can't edit views. I'm fascinated this hasn't been fixed, for me, it's a huge reason not to work with mysql.

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Query Browser into MySQL Workbench. We won't add this feature request anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/

I have the same bug with MySQL WorkBench

Why is this marked with "Won't fix"?

It's a very obvious bug. You can't edit views currently, and that's kind of a big deal when you have a large query being displayed on one single line.

It's extremely frustrating to see that this bug was submitted well over 5 years ago. If this won't get fixed, then please point me in the direction of a software package that allows you to properly edit a view.