I don't think I understand how you reconcile Mailman's load/save transaction units with sql's transaction.
There are places in mailman where a list is loaded and manipulated, but not saved... ...does your code basically change the semantics so that effectively a "save" happens after every single state change, yet the "save" method is a no-op? --- Dale Newfield <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little safety deserve neither liberty nor safety." - Benjamin Franklin, on the Statue of Liberty _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
