Hum, All tables are InnoDB, maybe when was the time of 2.0x and MyISAM, and I upgraded to 2.1x I missed the foreign keys, they are really missing. This is some Mailbox thas was deleted (of course). I'm going to check every table (test your comparation example) and apply the missing one's, and then upgrade again and I'll let you know the result, if successful or not.
Jorge -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul J Stevens Sent: terça-feira, 5 de Fevereiro de 2008 13:32 To: DBMail mailinglist Subject: Re: [Dbmail] DBMail 2.3.2 released Paul J Stevens wrote: > The fact that this could happen at all, means you either are running with MyISAM > tables, or your foreign key restrictions are not (fully) in place. Jorge, a quick follow up: My advice is to do as always when in doubt about schema consistency: mysqladmin create testdbmail1 mysqladmin create testdbmail2 mysqldump -d dbmail | mysql testdbmail1 ## dump your live schema cat sql/mysql/create_tables.mysql | mysql testdbmail2 mysqldump -d testdbmail1 > /tmp/testdbmail1.sql mysqldump -d testdbmail2 > /tmp/testdbmail2.sql diff -u /tmp/testdbmail1.sql /tmp/testdbmail2.sql This procedure should tell you where your 'live' schema differs from the default dbmail schema. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
