Paul J Stevens wrote:
Matthew T. O'Connor wrote:
I've now gotten things to the point where I'm running dbmail-util -by
after running the migration sql script. Thing appear to be working ok,
though it is taking quite a while (about an hour and a half so far), but
I'm getting these errors semi-frequently:
dbpgsql.c, db_query: Error executing query [INSERT INTO
dbmail_referencesfield (physmessage_id, referencesfield) VALUES
(514649,'[EMAIL PROTECTED]')] : [ERROR: duplicate key violates
unique constraint "dbmail_referencesfield_1"
]
dbmail-message.c,insert_field_cache: insert referencesfield failed
[INSERT INTO dbmail_referencesfield (physmessage_id, referencesfield)
VALUES (514649,'[EMAIL PROTECTED]')]
Is this normal? Can this be ignored?
You will most likely see similar duplicate key violations on the
headervalue table as well. I couldn't think of a better way to handle
this. Mysql will let you do 'REPLACE INTO' but postgres and sqlite do
not. Doing a 'SELECT' before *every* 'INSERT' seemed like excessive.
OK, so this is not a problem, right?