ZPsycopgDA getcursor() returns uninitialized connections if called from a separate thread
Reported by Daniele Varrazzo | April 2nd, 2013 @ 12:15 AM
Manually creating a thread and calling getcursor() from there returns a cursor on a connection that didn't receive the 'init' procedure (isolation level, encoding, typecasters).
Reported by zagy in https://github.com/psycopg/psycopg2/pull/2
For the moment the bug won't be fixed, at least not in the
invasive way proposed above. An easy workaround is to explicitly
getconn().cursor() instead of
If you are affected by this bug please add a comment, thank you.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Psycopg is the most used PostgreSQL adapter for the Python programming language. At the core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.