This project is archived and is in readonly mode.
IntegrityError constraint_name is empty with postgres-9.1
Reported by Dan Milon | April 10th, 2014 @ 10:14 PM
We experienced this weird behaviour. An IntegrityError was raised (due to a foreign key constraint failing) by psycopg.
Under postgres-9.1 .diag.constraint_name is
None.
Under postgres-9.3 .diag.constraint_name is properly
set to the name of the constraint.
Is this expected?
Comments and changes to this ticket
-
Daniele Varrazzo April 10th, 2014 @ 11:29 PM
- State changed from “new” to “invalid”
Yes, it is expected. constraint_name is one of the diag fields that were added to PostgreSQL 9.3.
-
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
<b>WARNING:</b> the informations in this tracker are archived. Please submit new tickets or comments to <a href="https://github.com/psycopg/psycopg2/issues">the new tracker</a>.
<br/>
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.
Dan Milon
Daniele Varrazzo
Federico Di Gregorio