Hello, One more time - in my second patch for this fixed the race condition with simultaneous inserts, but I left out the fix for delivering to multiple recipients. This one does both (it doesn't seed rand() because it only uses it for a changing/unique value). It's been running fine for 16 hours now on our system. If someone could think of a way to get a truely unique value across multiple machines, between multiple processes on one machine, and can eg. be incremented per recipient in a single message, it'd be better (eg. select some uniqueness from the common database server to seed rand(), or...).
Jesse > unique_id fix (*) Jesse Norell tmp-empty value > fails with db constraints -- Jesse Norell [EMAIL PROTECTED]
unique_id.patch
Description: Binary data
