On Tue, Sep 04, 2001 at 01:17:25AM +0200, Federico Di Gregorio wrote:
| you have three solutions here:
|
| 1/ commit() just before SELECT;
|
| 2/ use a single connection, all the cursor derived from it will see
| the changes to the data immediately;
|
| 3/ put the connection you what to use for select on autocommit mode,
| that will remove any isolation from that connection and let it see
| changes done to the db just after they are committed (note that
| autocommit() will be deprecated in favor of a generic
| isolation_level() method in the 1.x series).
4/ In the DbPool.py code add a "Rollback()" call to the
connection wrapper object when it gets returned to
the connection pool.
This bug has bitten me as well; I'm a bit too busy to
think through a more general solution now; but in
about 2-3 weeks when I get a breather I've signed up
to fix the DbPool in a thoughtful manner... right now
the rollback hack works...
Best,
Clark
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
