Django

Code

Ticket #9763 (closed: duplicate)

Opened 1 year ago

Last modified 1 year ago

is_dirty() in the transactions middleware blocks commit for Postgre

Reported by: Jeffrey Assigned to: nobody
Milestone: Component: Database layer (models, ORM)
Version: 1.0 Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

In its default operation Postgre makes a shadow copy of a table for reading, and this persists until you explicitly commit your transaction. However, the TransactionsMiddleware? class only calls commit when transaction.is_dirty() returns true. If you only read from the database, commit will never get called.

Possibly the is_dirty() check should be bypassed (or perhaps always return True) for postgres.

Attachments

Change History

12/05/08 21:57:09 changed by Jeffrey

  • needs_better_patch changed.
  • needs_tests changed.
  • needs_docs changed.

See:

01/05/09 08:27:01 changed by shai

PostgreSQL here is just a special case; the behavior is wrong everywhere. See #9964.

02/26/09 19:29:56 changed by jacob

  • status changed from new to closed.
  • resolution set to duplicate.

Duplicate of #9964.

Add/Change #9763 (is_dirty() in the transactions middleware blocks commit for Postgre)




Change Properties
Action