Re: duplicate entry error on primary key? further investigation
On further investigation it turned out ,in my case anyway, that the error had nothing to do with UTF-8. It wasn't random neither.
The access database from which I migrated to MySQL was a replica. One of the replication fields, s_GUID , which (as I understand it) generates a unique replication ID code, triggered the duplicate entry error.
Altough the code is in this field is unique, the Migtation Tool somehow interpretes it as being duplicate and responds with an error message, because in this field no duplicates are allowed.
My solution was to alter in the Access database the s_GUID field setting to allow duplicates. Note that this is tricky if you still want to use the old access database with replication.
Subject
Written By
Posted
February 02, 2008 04:26PM
February 03, 2008 01:14PM
Re: duplicate entry error on primary key? further investigation
May 08, 2008 09:50AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.