This is unexpected behaviour. If you've setup the foreign key restraints
correctly, there should never be an entry in dbmail_messages that doesn't point
to a record in physmessages.
Of course, it *is* possible to delete the messageblks belonging to a physmessage
without actually deleting the physmessage record. But it would be a bug if any
of the dbmail tools would do so.
Nate Zabaldo wrote:
Innodb is what I am using. Would it matter if I was using MyISAM?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Paul J Stevens
Sent: Sunday, January 16, 2005 1:03 AM
To: DBMail mailinglist
Subject: Re: [Dbmail] Orphans
What database are you using? And if mysql, what table type?
Nate Zabaldo wrote:
Thanks. -y fixed the mailbox problem. I still am trying to understand
how there can be records in dbmail_messages without a related record
in dbmail_physmessage or dbmail_messageblks. Any ideas?
Thanks again, Nate
Paul J Stevens wrote:
Have you tried *adding* the -y switch? dbmail-util -y -t to signify
that
actions must actually be performed?
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands_______________________________________www.nfg.nl
