| Bug #87459 | Apostrophe or Single Quote not escaped during migration | ||
|---|---|---|---|
| Submitted: | 17 Aug 2017 16:52 | Modified: | 18 Aug 2017 16:36 |
| Reporter: | Jon Nyman | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Workbench: Migration | Severity: | S3 (Non-critical) |
| Version: | 6.3.8 | OS: | Windows (10 Creators Edition) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | apostrophe, migration, single quotation, workbench | ||
[17 Aug 2017 16:59]
Jon Nyman
Workbench Error Log
Attachment: Workbench-Log.txt (text/plain), 3.63 KiB.
[17 Aug 2017 21:33]
MySQL Verification Team
Thank you for the bug report. Please try current release version 6.3.9.
[18 Aug 2017 16:06]
Jon Nyman
Using 6.3.9 worked. I guess Chocolatey has an old version in the repo.
[18 Aug 2017 16:36]
MySQL Verification Team
Thank you for the feedback.

Description: In SQL Server I have a field with type `nvarchar(max)` and in that field let's say that I have this content "blah, he's blah" with an apostrophe. When using the migration tool it fails since it doesn't escape the apostrophe. How to repeat: Create a database in SQL Server Developer Edition 2016. Then create the table with content: CREATE TABLE Test ( ID INT NOT NULL IDENTITY(1,1) PRIMARY KEY , String NVARCHAR(MAX) NOT NULL ) INSERT INTO Test (String) VALUES ('This is a test.') , ('With single quotation '' yep.') , ('No single here.') Suggested fix: Escape the quotations in `nvarchar`/`varchar`/`char`/`nchar` data types.