Bug #66942 wrap-lines option not present in procedure/function editors
Submitted: 24 Sep 2012 7:36 Modified: 13 Jun 2013 20:49
Reporter: Pankaj Agarwal Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.42, 5.2.43 OS:Windows
Assigned to: CPU Architecture:Any
Tags: wrap-lines option not present

[24 Sep 2012 7:36] Pankaj Agarwal
Description:
wrap-lines option is not present in the functions/procedures editor, where-as it is there in normal SQL editors

How to repeat:
1. alter a function 
the wrap-line option is no-where to be seen

Suggested fix:
Please provider a wrap-line option in function/procedure editor
[24 Sep 2012 11:44] MySQL Verification Team
Thank you for the bug report. Please check for duplicate with http://bugs.mysql.com/bug.php?id=64714 . Thanks.
[25 Oct 2012 1:00] Bugs System
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".
[25 Oct 2012 4:11] Pankaj Agarwal
no, this isn't same as http://bugs.mysql.com/bug.php?id=64714
this issue occurs when you try to alter a stored procedure/routine using mysql workbench. In the previous versions there used to be a wrap-line option when you right-clicked on the editor, but its not present there anymore
[25 Oct 2012 14:22] Armando Lopez Valencia
Thanks for your report.
Verified in:
Windows 7x64
WB 5.2.40
WB 5.2.44 rev 9933

Repro Steps:
1. Open a SQL connection.
2. Right click on a function/procedure and select the "Alter procedure" option.
3. Right click in the editable part of the function.
Actual Results:
The "Wrap-Lines" option is not available.
This option is available in WB 5.2.40
[13 Jun 2013 20:49] Philip Olson
Fixed as of the upcoming MySQL Workbench 6.0.2 public beta release, and here's the changelog entry:

The "Wrap-Lines" feature was not present in the functions/procedures
editor, but was available in the standard SQL editor. It is now available
to all SQL editors.

Thank you for the bug report.