pg8000

cursor "pg8000_portal_xxx_xxx" already exists

Bug #230784 reported by Mathieu Fenniak
2
Affects Status Importance Assigned to Milestone
pg8000
Status tracked in Trunk
Trunk
Fix Released
Medium
Mathieu Fenniak
pg8000 sqlalchemy

Bug Description

When using the DBAPI, it appears to be possible to redefine a portal with the same ID. Unknown what might cause this.

Can be reproduced running SQLAlchemy engine transaction tests.

Related branches

lp:pg8000
Revision history for this message
Mathieu Fenniak (mfenniak) wrote :

Some SQLAlchemy tests that fail:
  engine.reconnect.InvalidateDuringResultTest.test_invalidate_on_results
  engine.transaction.TLTransactionTest.testmorerollback_off_conn
  engine.transaction.TLTransactionTest.testrollback_off_conn

Changed in pg8000:
assignee: nobody → mfenniak
importance: Undecided → Medium
milestone: none → sqlalchemy
status: New → Confirmed
Revision history for this message
Mathieu Fenniak (mfenniak) wrote :

Fix released in pg8000 v1.05.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.