| Bug #50039 | With Access Foreign Key, Not valid escape sequence | ||
|---|---|---|---|
| Submitted: | 4 Jan 2010 2:46 | Modified: | 5 Jan 2010 8:12 |
| Reporter: | Jose M. delahuerga | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 1.1.17 | OS: | Windows (2003) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | access, foreign, migration | ||
[5 Jan 2010 8:12]
Susanne Ebrecht
Many thanks for writing a bug report. We are just on the way to implement full functionality of MySQL Migration Toolkit into MySQL Workbench. The existing Migration Toolkit is very old and our development is not supporting anymore. More information about Workbench you will find here: http://dev.mysql.com/workbench/
Description: When you do a migration from one Access BD with tables whose foreign key is called {18135814-296A-47E2-9788-A77E24} gives the following error: Not a valid escape sequence: {18135814-296A-47E2-9788-A77E24 (attention to the brackets on the right) How to repeat: 1. Create an Access DB: accessDb1.mdb 2. Create two tables in accessDb1.mdb and make a foreign key 3. Creates a second Access DB: accessDb2.mdb 4. From accessDb2 import tables and relations of accessDb1.mdb 5. Try to migrate with MySQL Migration Toolkit Suggested fix: When you import tables and relationships from an Access DB to another, Access renames the MSysRelationships.szRelationship field with a key value {....} MySQL Migration Toolkit seems ignorant the last '}'