Skip site navigation (1) Skip section navigation (2)

python - pq: Change state progression method.

From: jwp(at)pgfoundry(dot)org (James William Pye)
To: pgsql-committers(at)postgresql(dot)org
Subject: python - pq: Change state progression method.
Date: 2005-09-21 04:45:05
Message-ID: 20050921044505.201741125F69@pgfoundry.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Change state progression method. State is now progressed using the '>>'
operator, as opposed to directly setting the state. This creates a "transaction
protocol" that base Transactions need to implement. Really, it's not much better
than a named method, save it's apparent immutability(?).

Also, remove the error checking from client3.Transaction.__call__. This requires
that a Transaction be able to handle the error, or validate the type. This
allows transactions to actually handle errors, and to give more informative
tracebacks when a regular error occurs.

Make Function a bit more formal about its attributes and methods.

Modified Files:
--------------
    pq/src:
        client3.py (r1.10 -> r1.11)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/client3.py.diff?r1=1.10&r2=1.11)
        transam.py (r1.6 -> r1.7)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/transam.py.diff?r1=1.6&r2=1.7)
    pq/test:
        client3.py (r1.6 -> r1.7)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/test/client3.py.diff?r1=1.6&r2=1.7)

pgsql-committers by date

Next:From: James William PyeDate: 2005-09-21 07:16:14
Subject: python - typ: Imported Sources
Previous:From: Bruce MomjianDate: 2005-09-20 21:43:08
Subject: pgsql: Fix interaction between psql \set AUTOCOMMIT and

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group