[Pypgsql-devel] [ pypgsql-Bugs-1524586 ] Don't use transactions by default

[SourceForge.net <no...@so...>]

Bugs item #1524586, was opened at 2006-07-18 11:01
Message generated for change (Comment added) made by ballie01
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: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: BjLindqvist (sonderblade)
>Assigned to: Billy G. Allie (ballie01)
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.

----------------------------------------------------------------------

>Comment By: Billy G. Allie (ballie01)
Date: 2007-04-05 00:12

Message:
Logged In: YES 
user_id=8500
Originator: NO

The DB-API standard specifies that transaction be enabled by default
(autocommit off).  You can enable autocommit on a connection by executing
'connection.autocommit = True' before you execute a query.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1524586&group_id=16528