PostgresqlMessage
Related Doc:
package server
The SQLSTATE code for the error.
The SQLSTATE code for the error.
Not localizable. Always present.
http://www.postgresql.org/docs/current/static/protocol-error-fields.html
http://www.postgresql.org/docs/current/static/errcodes-appendix.html
The name of the column.
The name of the column.
If the error was associated with a specific table column, the name of the column. (Refer to the schema and table name fields to identify the table.)
The name of the constraint.
The name of the constraint.
If the error was associated with a specific constraint, the name of the constraint. Refer to fields listed above for the associated table or domain. (For this purpose, indexes are treated as constraints, even if they weren't created with constraint syntax.)
The name of the data type.
The name of the data type.
If the error was associated with a specific data type, the name of the data type. (Refer to the schema name field for the name of the data type's schema.)
A secondary error message carrying more detail about the problem.
A secondary error message carrying more detail about the problem.
It is possible for this message to run multiple lines.
The file name of the source-code location where the error was reported.
The file name of the source-code location where the error was reported.
A optional suggestion what to do about the problem.
A optional suggestion what to do about the problem.
This is intended to differ from Detail in that it offers advice (potentially inappropriate) rather than hard facts. Might run to multiple lines.
Indicates an error cursor postion as an index of an internally generated command.
Indicates an error cursor postion as an index of an internally generated command.
This is defined the same as position, but it is used when the cursor position refers to an internally generated command rather than the one submitted by the client. The internalQuery field will always appear when this field appears.
The text of a failed internally-generated command.
The text of a failed internally-generated command.
This could be, for example, a SQL query issued by a PL/pgSQL function.
The line number of the source-code location where the error was reported.
The line number of the source-code location where the error was reported.
The primary human-readable error message.
The primary human-readable error message.
This should be accurate but terse (typically one line).
Always present.
http://www.postgresql.org/docs/current/static/protocol-error-fields.html
Indicates an error cursor position as an index into the original query string.
Indicates an error cursor position as an index into the original query string.
The field value is a decimal ASCII integer, indicating an error cursor position as an index into the original query string. The first character has index 1, and positions are measured in characters not bytes.
The name of the source-code routine reporting the error.
The name of the source-code routine reporting the error.
The name of the schema containing that object.
The name of the schema containing that object.
If the error was associated with a specific database object, the name of the schema containing that object, if any.
The severity of the Error or Notice
The severity of the Error or Notice
The field contents are ERROR, FATAL, or PANIC (in an error message), or WARNING, NOTICE, DEBUG, INFO, or LOG (in a notice message), or a localized translation of one of these.
The name of the table.
The name of the table.
If the error was associated with a specific table, the name of the table. (Refer to the schema name field for the name of the table's schema.)
An indication of the context in which the error occurred.
An indication of the context in which the error occurred.
Presently this includes a call stack traceback of active procedural language functions and internally-generated queries. The trace is one entry per line, most recent first.
Represents an error that occured on the Postgresql Server.
The value members here are possible fields that can be appear in an
ErrorResponseorNoticeResponse.severity,code,detailare always present.http://www.postgresql.org/docs/current/static/errcodes-appendix.html
http://www.postgresql.org/docs/current/static/protocol-error-fields.html