From: | Martin Gregorie <martin(at)gregorie(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Complex transactions without using plPgSQL Functions. It is possible? |
Date: | 2012-03-07 11:55:40 |
Message-ID: | 1331121340.1747.36.camel@zappa.gregorie.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2012-03-07 at 14:19 +0400, Sergey Konoplev wrote:
> On Tue, Mar 6, 2012 at 11:30 PM, Andre Lopes <lopes80andre(at)gmail(dot)com> wrote:
> > This is the plPgSQL code that I need to write in Python. It is
> > possible to do this without using PlPgSQL?
>
Have you looked at pyodbc?
ODBC will usually accept statements allowing you to turn autocommit off
and to use connection.commit() to group a set of statements into a
transaction.
Note that there's a documentation comment saying that autocommit
settings are not passed to the driver, However, as the documentation is
still talking about bytea fields it may be out of date so I'd suggest
running a test. Try writing a Python test program that turns autocommit
off and does a couple of inserts followed by a rollback. File a bug if
the inserted data is in the table after a successful run.
Martin
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2012-03-07 12:34:08 | SQL Normalization Thought |
Previous Message | mdione.ext | 2012-03-07 10:27:46 | Re: ERROR: could not find tuple for trigger 37463634 |