Jan Rychter wrote:
> I've just hit a problem, as I have a transaction that I know will > sometimes fail and can be safely retried (see my blog post > http://jan.rychter.com/enblog/2009/6/6/postgresql-transactions.html for > details). Unfortunately, as weblocks encloses every request in a giant > transaction, my transaction has no effect, as they can't be nested. And > I'd venture a guess that just retrying the whole-request-transaction is > a bad idea, as there are plenty of side effects all over the code, > rendering being one of them. > > Do we need more fine-grained transaction control? Why can't you use a Postgres savepoint? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
