-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 George Sexton wrote: > I thought transactions were one of those features MySQL decided that > real developers didn't need. Are you really certain mySQL Supports > transactions in the relatively low version you are using?
I assume the poster meant MySQL-3.23, and yes, even MySQL-3.23 has transaction support. You need to use InnoDB tables to have transactional semantics, and it's all covered in the MySQL manual at: http://www.mysql.com/doc/en/ANSI_diff_Transactions.html and http://www.mysql.com/doc/en/ANSI_diff_Transactions.html > > Also, I hope you don't need to scale. You are essentially locking the > table until the mail goes or fails. What if it wedges for 60 seconds > doing a DNS lookup? With InnoDB, it would be a row-level, lock, however.... I agree. SMTP is not a 'transactional' resource. You might be better off dealing with failures after you detect them and rethinking your logic here, instead of waiting for your mailserver to tell you whether it accepted the message or not. Even if your mailserver accepts the message, there is no 'transactional' guarantee that it will be delivered. You'll need to watch for 'bounce' messages to see whether it was delivered or not, and even then, you might not get those. Perhaps a better way to do it might be to have different states, i.e. confirmation email sent, user confirmed, etc? Regards, -Mark - -- Mr. Mark Matthews MySQL AB, Software Development Manager, J2EE and Windows Platforms Office: +1 708 557 2388 www.mysql.com Are you MySQL Certified? http://www.mysql.com/certification/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQE/4zYktvXNTca6JD8RApvwAKC3tM1FwsDk0oKbOr/mjGr7czCdUgCgrMcu 3HHtgH4skyOukBRC6RRqMIk= =OxcC -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
