Re: transactions and locking in postgreSQL

On Dec 5, 10:43 pm, Jeffrey Straszheim <[EMAIL PROTECTED]> wrote: > I took a quick glance at transaction.py (where the TransactionMiddleware > class is defined), and it appears you are correct. However, it should > be pretty easy to roll your own transaction class that skips the > is_dirty check.

Re: transactions and locking in postgreSQL

msoulier wrote: > Looking at the transaction middleware that wraps a transaction around > every HTTP request, I've found that it only commits if the transaction > is "dirty" (you change something). > > So, if you use this middleware unconditionally, then in view functions > that only read, the tra

transactions and locking in postgreSQL

Looking at the transaction middleware that wraps a transaction around every HTTP request, I've found that it only commits if the transaction is "dirty" (you change something). So, if you use this middleware unconditionally, then in view functions that only read, the transaction will never be comm