MySQL Bugs: #57861: SHOW CREATE fails to linebreak after #comment

Bug #57861	SHOW CREATE fails to linebreak after #comment
Submitted:	30 Oct 2010 9:31	Modified:	18 Dec 2010 20:31
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.1.51	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
A user of ours reports here that SHOW CREATE PROCEDURE fails to add a linebreak after a #comment.  The statement cannot be imported due to this. In next try it worked OK for our user. 

While working with this I experienced the same once (1 try out of around 40 I guess) on MySQL 5.1.51 64bit for Windows.  I have not been able to reproduce it again. It seems to be a hard-to-reproduce issue that SHOW CREATE sometimes randomly fails to add a linebreak after a #comment.

How to repeat:
Details (including a sample CREATE statement) here:
http://www.webyog.com/forums/index.php?showtopic=5371

User generated a backup with SQLyog (failed first tiem as describe, worked OK next time), but when I had same issue I was just executing SHOW CREATE PROCEDURE. 

Suggested fix:
No idea. I am not able to identify specific circumstances resulting in this.

Thank you for the report.

I can not repeat described behavior with procedure described at http://www.webyog.com/forums/index.php?s=f1a6ec3b03f354ee20915d6c4a144aab&showtopic=5371&v... Please try with current version 5.1.52 and if problem still exists provide repeatable test case.

@Sveta .. I cannot either. I think I told that I am not able to identify circumstances leading to this. Also I am mystified by this myself.  But we have one user experiencing this once.  And also I am almost sure I did once.

I believe code review would be the only way.  And if you want me to contribute with that please provide me a MySQL server coded in SIMULA (I am an old man, you know - you have met me once!). :-)

If you have tried what can be considered a 'reasonable effort and thinking' to reproduce this - and with no luck - it is OK to set as "can't repeat".  Should I ever bump into more information about this - or notice another related - report here, I will contact you again.

Thank you for the feedback.

Could you please ask user to provide their dump and information about how they created the procedure. Did they use older version of MySQL server?

I will try in the weekend or by beginning of next week to contact him. 
I cannot guarantee that he will respond.

Thank you for this. We will wait feedback from your side.

This bug also reminds me bug #55557

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".