Bug #58886 When trying to paste multiple lines in a text field only first line gets copied.
Submitted: 11 Dec 2010 23:27 Modified: 4 Feb 2015 0:09
Reporter: Chirag Patel Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.31 OS:Windows
Assigned to: CPU Architecture:Any
Tags: paste, sql editor, workbench

[11 Dec 2010 23:27] Chirag Patel 
Description:
When I'm trying to paste this into a 'text' field in a column

<ul>
  <li>Windows XP</li>
  <li>Windows Vista</li>
  <li>Windows 7</li>
  <li>Windows 98</li>
</ul>

It does not copy the whole data set instead it copies only the first line <ul>

How to repeat:
Create a new database with 4 -5 fields and keep one of them as a text field then use CTRL + V to paste following data

<ul>
  <li>Windows XP</li>
  <li>Windows Vista</li>
  <li>Windows 7</li>
  <li>Windows 98</li>
</ul>
[13 Dec 2010 9:12] Valeriy Kravchuk 
Thank you for the problem report. Verified with 5.2.31 on Windows XP.
[16 Dec 2010 23:31] Alfredo Kojima 
You should use the field editor dialog to paste multi-line text.
[17 Dec 2010 17:16] Johannes Taxacher 
the grid control used, does not support multiline content, we added a content editor (also used for viewing binary data and images) to handle multiline strings. right-click the cell (when its selected, but not in edit mode) and click "open value in editor".

we'll keep the report as feature request to improve that in future versions.
[24 Feb 2012 17:46] Craig Fowler 
Could I suggest that this feature was successfully actioned in-or-before 5.3.38?  I am using that version on Linux and the EDIT table UI permits multi-line paste (as well as the aforementioned value editor).
[4 Feb 2015 0:09] Philip Olson 
Posted by developer:
 
There isn't anything to document here, as this was fixed long ago (multiple line input values are saved now) and the form editor was introduced in 6.1.0. The popup editor (right click on a field and choose 'Open Value in Editor') has also been around for a long time.

That said, I'm closing this old bug report. Sorry we are unable to determine when exactly this was fixed (I suspect in 5.2.xx) but at least it's fixed. :-)