Bug #3679 Access violation at address # in module 'LIBMYSQL.dll'
Submitted: 6 May 2004 20:16 Modified: 10 May 2004 16:01
Reporter: [ name withheld ] Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.0.3 ALPHA OS:Windows (Windows XP Pro)
Assigned to: CPU Architecture:Any

[6 May 2004 20:16] [ name withheld ] 
Description:
This is certainly a DUP of bug#3526, but since that one is marked as "Can't Repeat", I thought this to be the only way to reopen the bug.

I did a backup from MySQL 3.23.41 (platform?) and restored to MySql
4.0.16-standard on Linux via the MySQL Administrator GUI. I received this error
when it was importing data on a particular table. All other data was imported.
It appears to have broken on a certain row, because only 27 of 329 records were
imported for that particular table. Records with "day" values up to "3:1" are
inserted, then the restore breaks. Here is the relevant section of the backup
xml file (sorry it so lengthy, but I wanted to post the two full lines of
relevant data):

How to repeat:
Repeating this is going to be difficult. I will add a SQL file that can be used to Restore and should allow someone to reproduce the error.
[6 May 2004 20:26] [ name withheld ] 
Oops, my original post should say "sql file", not "xml file".
[10 May 2004 16:01] Alexander Keremidarski 
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

Please follow original bug report instead of opening new one. As soon as we have repeatable test case we will reopen it.