|
From: Billy G. A. <bil...@de...> - 2006-04-03 03:21:50
|
On Sun, 2006-04-02 at 19:25 +0100, Terry Macdonald wrote:
> Billy G. Allie wrote:
> > On Mon, 2006-03-27 at 13:52 +0100, Terry Macdonald wrote:
> >> Hi,
[ . . . ]
> >
> If I have understood you then If I have a single cursor on a connection
> I would need to do a commit after every select so that a subsequent
> insert or update would have a correct timestamp.
> Or...
> I could have two connections each with a cursor; one connection/cursor
> pair would be used for non-select statements and the other
> connection/cursor pair would be used for selects
>
> Yes?
>
Either would work (providing that the connection/cursor pair used for
inserts and updates is commited frequently enough to make the timestamps
reflect the current time.
Note that the restrictions of one active transaction per connection is a
PostgreSQL restriction, not a DB-API 2.0 compilant module restriction.
|