From: SourceForge.net <no...@so...> - 2006-07-18 15:01:21
|
Bugs item #1524586, was opened at 2006-07-18 17:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1524586&group_id=16528 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: PgSQL Group: None Status: Open Resolution: None Priority: 5 Submitted By: Björn Lindqvist (sonderblade) Assigned to: Nobody/Anonymous (nobody) Summary: Don't use transactions by default Initial Comment: Today I spent alot of time tracking down why my updates to the database didn't seem to stick. It appears the problem was that pyPgSQL uses transactions by default. Wrapping the queries in BEGIN WORK/COMMIT WORK statements fixed the problem. To prevent others from running into the same annoyance I suggest that transactions should be off by default. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1524586&group_id=16528 |