Bug #44983 Server drops comment after "END" + formating issues
Submitted: 20 May 2009 12:49 Modified: 23 May 2009 22:08
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1.34 OS:Windows (probably any)
Assigned to: CPU Architecture:Any
Tags: qc

[20 May 2009 12:49] Peter Laursen
I attach images (SQLyog and command line screenshots).  This is difficult to explain in words alone and formatting points may be lost in HTML!

How to repeat:
se images!

Suggested fix:
1) a comment after "END" is a valid as any comment I think?

2) please preserve the formatting for the CREATE statement as defined by user.
[20 May 2009 12:50] Peter Laursen
example in SQLyog

Attachment: sqlyog.jpg (image/jpeg, text), 87.35 KiB.

[20 May 2009 12:51] Peter Laursen
example in command line client

Attachment: cmdline.jpg (image/jpeg, text), 73.53 KiB.

[20 May 2009 13:08] Valeriy Kravchuk
Item 1 is more a question to SQLyog's developers :) Does it send comment after END$$ to server at all? mysql command line client just skips them all...

Item 2 is a reasonable feature request, IMHO.
[21 May 2009 23:21] Omer Barnir
The 'aspects' of this bug relating to the formatting of the output are a feature request. The aspect relating to the ast comment not showing is not a bug as the comment is after the END and is not part of the function definition
[23 May 2009 22:08] Peter Laursen
@Omer .. 

Your point as regards the comment after END is a very valid point (and as such accepted!).  But I do not understand the carelessnes in MySQL organisation about usability issues (and formatting is important for usability for most users). As a vendor providing sotwar fot the MySQL server we constantly get complaints from our users about this (who do not understand what are server issues and what are client issues).

Also "Omer" is not "   O   mer" :-)