Deletion/record visibility error in PG with Python...

[Durumdara]

Hi!

Sorry for rtfm mail... I forgot to remove max_usage param in my real
application...

This parameter is limiting the number of cursor usage, and if max reached,
the DBUtils is automatically open a new cursor in the background! This is
break out of the actual transaction context...

Uhhhhh.... I wasted 2 hours to found the bug in another source... :-(

dd

2009/5/28 Durumdara <durumdara at gmail.com>

> Hi!
>
> PGSQL makes me crazy...
>
> I port my apps to PGSQL, and I near to finish - but I got this problem...
>
> Params: PGSQL 8.3, Windows, Pylons, PGDB, DBUTILS...
>
>
> What happened? How I can avoid the cursor changing? How to fix it in my
> transaction?
> I never ask for new cursor, I used same variable in all of my context
> (self.Cur)... :-(
>
> So what is the solution? Drop DBUtils? Or what?
>
> Thanks for your help:
>     dd
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20090529/a14a2a3d/attachment.html>