Opened 16 years ago

Closed 15 years ago

#9763 closed (duplicate)

is_dirty() in the transactions middleware blocks commit for Postgre

Reported by: Jeffrey Owned by: nobody
Component: Database layer (models, ORM) Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


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.

Change History (3)

comment:2 by Shai Berger, 15 years ago

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

comment:3 by Jacob, 15 years ago

Resolution: duplicate
Status: newclosed

Duplicate of #9964.

Note: See TracTickets for help on using tickets.
Back to Top