On Nov 26, 2010, at 2:26 PM, Jacek Kałucki wrote:
> As you know, psycopg2 uses implicit transactions.
> Unfortunately, it causes that once per hundred writes
> I loose my my data.
> Here is the excerpt from backend log: http://dabo.codepad.org/ICZonfLB
> There is warning message "there is no transaction in progress" after second
> commit and my data flies away occasionally.
> Is this possible that you add explicit transactions support
> to PostgreSQL backend?
I believe that issuing a second 'BEGIN' will not harm anything,
although it may generate a warning. Can you try changing the beginTransaction
method in dbPostgreSQL.py to issue:
cursor.execute("BEGIN")
... and let me know how that works?
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
