So why 'upgrade' to mysql-5.1? Mentioned message stinks! Make a schema dump of your database and take a long hard look at it! Or post it here, if you think that's appropriate.
And start planning a downgrade to 5.0 if 5.1 turns out to be buggy (again/still/forever). On 10/07/2010 02:36 PM, Reindl Harald wrote: > Hm this should be unchanged since last summer > and some days before with mysql 5.0.50 > unconnected messages were removed successfully > > Am 07.10.2010 14:32, schrieb Paul J Stevens: >> On 10/07/2010 01:12 PM, Reindl Harald wrote: >>> Has anybody the same messages since MySQL 5.1? >>> The last days it was only one, the second since tonight >>> _____________________ >>> >>> Repairing DBMAIL physmessage integrity... >>> Ok. Found [2] unconnected physmessagesWarning: could not delete orphaned >>> physmessages. Check log. >>> >>> InnoDB: Cannot delete/update rows with cascading foreign key constraints >>> that exceed max depth of 250 >>> Please drop excessive foreign constraints and try again >> >> That sounds like a circular key restraint. Better check your schema! > > > > > _______________________________________________ > DBmail mailing list > [email protected] > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
