Bug #75392 | Multiline comments treated inconsistently | ||
---|---|---|---|
Submitted: | 2 Jan 2015 14:45 | Modified: | 19 Jan 2015 16:03 |
Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
Version: | any - case from 5.6.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Jan 2015 14:45]
Peter Laursen
[2 Jan 2015 14:54]
Peter Laursen
BTW: isn't "\n" odd in any case? I can understand the compliance with "/n" in C - even though I think it is completely misplaced here. The comment is *a string* simply.
[2 Jan 2015 15:21]
Peter Laursen
The alignment issue is a non-issue, I realize. The client cannot handle display of multiline strings. You will have to use "\G" and not ";" as statement separator/delimiter.
[2 Jan 2015 15:26]
Peter Laursen
mysql> SELECT `SPECIFIC_NAME`, ROUTINE_COMMENT FROM `information_schema`.`ROUTIN ES` WHERE SPECIFIC_NAME = 'testp'\G *************************** 1. row *************************** SPECIFIC_NAME: testp ROUTINE_COMMENT: this does nothing 1 row in set (0.01 sec) (I think still rather bad formatted!)
[3 Jan 2015 20:51]
Peter Laursen
I was wondering if the representation of linebreaks as "\n"ยด|"/n" is due to the historical linkage of MySQL with PHP somehow? Anyway an [LF] character is neither!
[19 Jan 2015 15:59]
MySQL Verification Team
Tested and it truly behaves as described. Fully verified, but it is not considered to have a serious impact.
[19 Jan 2015 16:03]
Peter Laursen
Nothing seems to matter then, right? This was a very disappointing reply.