Changes between Initial Version and Version 1 of Ticket #23292


Ignore:
Timestamp:
Aug 14, 2014, 11:07:00 AM (10 years ago)
Author:
ijl
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #23292 – Description

    initial v1  
    11When specifying `ATOMIC_REQUESTS` on a database, a connection is made to the database whether or not it is used. This is due to `BaseHandler.make_view_atomic` wrapping the view in a `transaction.atomic` for each database. Each call to `transaction.atomic` results in opening a database connection and then opening a transaction.
    22
    3 This is a serous performance regression for a project migrated from using `TransactionMiddleware` with many databases. The previous behavior was that a connection and transaction would be opened only for a database that the ORM needed to access.
    4 
    5 Is there any interest in modifying this to acquire connections and transactions lazily?
     3Is there any interest in modifying this to acquire connections and transactions only when the ORM attempts to use that database?
Back to Top