On coderrr's blog today, he mentions an issue with ActiveRecord transactions being committed instead of rolled back if Thread#kill is used (http://coderrr.wordpress.com/2011/05/03/beware-of-threadkill-or- your-activerecord-transactions-are-in-danger-of-being-partially- committed). Turns out that Sequel is subject to the same issue. I've committed a patch that fixes the issue on ruby 1.8 and rubinius (https://github.com/jeremyevans/sequel/commit/ 7e2a1c509cfa99a7c558f21b1c69b8f18f3a4bda). There currently is no reliable fix for ruby 1.9 and JRuby. If anyone has any ideas about how to handle those implementations, please let me know.
Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
