-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for PG_DIAG_*_NAME error fields #161
Comments
Original comment by Joe Van Dyk (Bitbucket: joevandyk, GitHub: joevandyk). http://www.depesz.com/2013/03/07/waiting-for-9-3-provide-database-object-names-as-separate-fields-in-error-messages/ has more btw. |
Original comment by masklinn (Bitbucket: masklinn, GitHub: masklinn). @ged psycopg doesn't really use the #5 thing for diagnostics, they added a new attribute to the root Psycopg exception, and that attribute links to an object bearing all diagnostic attributes. It's not limited to any specific kind of error. Although it is related to having a root exception type for the adapter, I don't know if pg has one. |
Original comment by Lars Kanis (Bitbucket: larskanis, GitHub: larskanis). The new Regarding to the |
Original report by Joe Van Dyk (Bitbucket: joevandyk, GitHub: joevandyk).
See related discussion here: http://psycopg.lighthouseapp.com/projects/62710/tickets/149
http://www.postgresql.org/docs/devel/static/libpq-exec.html#LIBPQ-PQRESULTERRORFIELD
The text was updated successfully, but these errors were encountered: