Bug #12210 save SQL create script
Submitted: 27 Jul 2005 15:34 Modified: 31 Jul 2005 20:02
Reporter: Frank Herrmann Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:1.0.11 beta OS:Windows (Windows XP)
Assigned to: CPU Architecture:Any

[27 Jul 2005 15:34] Frank Herrmann
Description:
I migrated a MS Access Database file to MySQL Server. Migration worked but a shell window opens repeating the same error message over and over when I select the option 'Create Script File for Create Statements'. The error message reads:

** (process:1952): CRITICAL **: file .\source\myx_grt_value.c: line 1355: assertion `dict != NULLĀ“ failed

I selected 'latin1' for Migration of type Schema and 'data consistency / multilanguage' for Migration of type Table.

A workaround is to deselect the option, select option 'Create Objects online' and copy and paste the 'message log' afterwards.

How to repeat:
I did not include all the details or any example files since it seems to be a general problem (migration works). I will provide more details if the error is not reproducible.
[28 Jul 2005 18:36] Jorge del Conde
Hi!

I can't reproduce this bug.  Can you tell me exactly what you did to receive that error ?

Thanks!
[29 Jul 2005 10:39] Richard Black
I've just experienced this problem too, although I've got 2 lines mentioned in the window that appears:

1355 and 3112. Both are apparently in the source file myx_grt_value.c.
[29 Jul 2005 12:36] Frank Herrmann
I provide a simple access 97 file debug.mdb - maybe the error depends on the access version. I stepped through the migration process up to the page where one can select 'Create Script File for Create Statements' . As Richard said there are two lines where the assertion fails: 1355 and 3112.
[29 Jul 2005 13:02] Michael G. Zinner
"I provide a simple access 97 file debug.mdb"

Did you upload the file on the Files page? I cannot find it there. It would help a lot if you could provide the file to repeat this. Thanks.
[31 Jul 2005 20:01] Jorge del Conde
I was unable to reproduce this bug using the included debug.mdb file:

mysql> show tables;
+-----------------+
| Tables_in_debug |
+-----------------+
| testtab         |
+-----------------+
1 row in set (0.00 sec)

mysql> desc testtab;
+-------+---------------------+------+-----+---------+----------------+
| Field | Type                | Null | Key | Default | Extra          |
+-------+---------------------+------+-----+---------+----------------+
| ID    | int(10)             | NO   | PRI | NULL    | auto_increment |
| foo   | varchar(50)         | YES  |     | NULL    |                |
| bar   | int(10)             | YES  |     | NULL    |                |
| baz   | tinyint(1) unsigned | NO   |     |         |                |
+-------+---------------------+------+-----+---------+----------------+
4 rows in set (0.03 sec)

mysql>