Aryeh Gregor wrote:
On Wed, Sep 1, 2010 at 2:42 AM, Maciej Jaros egil@wp.pl wrote:
I think it still should be conscious decision and so those functions could use their first... hm... second parameter as the transaction name. For MS SQL you can simply use BEGIN TRANSACTION [name] (I think it would be more natural), for MySQL I guess savepoints should be used.
I'm not sure what you're saying here. Are you suggesting some solution where commit() does not actually always commit the current transaction? If so, as I said, this is a problem because it will cause locks to be held for much too long in some cases.
Is there some way to find out those points were the commit needs to be there for lock freeing and not just for normal transaction finish ?