3 ms·

Care to explain what it is?

• ubernostrum 13y ago
  Currently, Django closes the database connection at the end of each request/response cycle. In 1.6, Django will optionally not do this; instead, a setting can specify the maximum amount of time to hold open and keep reusing an existing connection. This is not connection pooling; that would imply some functionality to actively maintain and allocate connections. This is simply "your process will hold its connection open from one request/response cycle to the next".
  • pajju 13y ago
    Thanks for the detailed answer. In what scenario can this be used?
    • mik3y 13y ago
      Think of it as an optimization: Previously, each request meant a new db connection had to be opened. Now a prior connection can be reused.