-------------- Original message ----------------------
From: johnf <jfabiani (AT) yolo .D.OT com>
> On Sunday 24 February 2008 08:08:10 pm Adrian Klaver wrote:
> > On Sunday 24 February 2008 7:50 pm, johnf wrote:
> > > On Sunday 24 February 2008 07:37:50 pm Adrian Klaver wrote:
> > > > Where do you see the error appear
> > >
> > > Where does it appear. Anytime I close my forms I see
> > > "Dabo Info Log: Sun Feb 24 19:38:22 2008: Application finished"
> > > And that's all.
> >
> > It is appearing in the Postgres log.
>
> Adrian,
> You have been following the discuss on the psycopg list. Have you any
> suggestion on how to handle the problem in Dabo?
>
> My testing has not provided a simple solution. Your suggested change only
> changes the error message from a dropped client to an abort. To be honest
> the error messages are not preventing Dabo from working but do imply
> something could go wrong in the future.
>
> BTW just adding a connection.execute("commit") does not prevent the error
> messages from Dabo.
>
> --
> John Fabiani
>
>
First off it would need to be connection.commit(). There are a couple of things happening here.
By default Psycopg runs in ISOLATION_LEVEL_READ_COMMITTED and starts a transaction everytime
an execute() is run (see docs for exceptions). It would be possible to have it run as
ISOLATION_LEVEL_AUTOCOMMIT which would solve your ABORT issue. The problem is that the
connection object does not have a begin() method to go with its commit() and rollback() methods, so it would
be necessary to execute() a "BEGIN;" if you want a transaction to span multiple statements. The post from
James on the Psycopg list would seem to indicate they may need to work on their clean up code to make
__del__ work properly. At this point I see no time frame on that. At this point as I far as I can tell the issue
is mostly noise in the logs. Unfortunately, my experience is that when you start ignoring the noise in the
engine too long bad things eventually happen. I will probably pursue a test case for the Psycopg guys
to see if they can patch on their end.
--
Adrian Klaver
aklaver@comcast.net
©2008 aklaver .AT. comcast .DO.T net (Adrian Klaver) |
