I removed any constraint from the database, and i still get the same error. also, grepping through sql script for dbmail setup shows lines like these: ALTER TABLE aliases_pkey RENAME TO dbmail_aliases_pkey; which is for the migration from 1.x to 2.x but the database itself does not actually have those tables - there is dbmail_aliases but not dbmal_aliases_pkey My script did import the aliases part of the db dump when i removed the autoincrement expression for aliases_idnr, but now i cannot import users, messages, mailboxes and messageblks tables, i get that same error for any of those tables. May be there is a sequence im missing, as in users need to be populated first, mailboxes second, etc? Thank you!
max --- Original Message --- From: Jesse Norell <[EMAIL PROTECTED]> Sent: Fri, 22 Apr 2005 15:52:05 -0600 (MDT) To: [email protected] Subject: RE: [Dbmail] database recovery > > > > error: > > DBD::Pg::st execute failed: ERROR: duplicate key violates unique > > constraint \"dbmail_aliases_pkey\" > > Cannot complete query: ERROR: duplicate key violates unique > > constraint \"dbmail_aliases_pkey\" > > There\'s a unique constraint on a column in the dbmail_aliases table > probably dbmail_aliases_idnr) and you\'re trying to insert 2 rows with > the same value in that field. Just increment a counter every time you > insert a row, and put that value into that field. > > > -- > Jesse Norell > jesse @ kci.net > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > >
