module PG::Constants - pg: The Ruby Interface to PostgreSQL

# module PG::Constants

### Constants

CONNECTION_AUTH_OK

  Received authentication; waiting for backend start-up to ﬁnish.

CONNECTION_AWAITING_RESPONSE

  Waiting for a response from the server.

CONNECTION_BAD

  Connection failed

CONNECTION_MADE

  Connection OK; waiting to send.

CONNECTION_NEEDED

  connect() needed.

CONNECTION_OK

  Connection succeeded

CONNECTION_SETENV

  Negotiating environment-driven parameter settings.

CONNECTION_SSL_STARTUP

  Negotiating SSL encryption.

CONNECTION_STARTED

  Waiting for connection to be made.

INVALID_OID

  Invalid OID constant

INV_READ

  Flag for lo_creat, lo_open – open for reading

INV_WRITE

  Flag for lo_creat, lo_open – open for writing

InvalidOid
PGRES_BAD_RESPONSE

  The server’s response was not understood.

PGRES_COMMAND_OK

  Successful completion of a command returning no data.

PGRES_COPY_BOTH
PGRES_COPY_IN

  Copy In (to server) data transfer started.

PGRES_COPY_OUT

  Copy Out (from server) data transfer started.

PGRES_EMPTY_QUERY

  The string sent to the server was empty.

PGRES_FATAL_ERROR

  A fatal error occurred.

PGRES_NONFATAL_ERROR

  A nonfatal error (a notice or warning) occurred.

PGRES_POLLING_FAILED

  Async connection failed or was reset

PGRES_POLLING_OK

  Async connection succeeded

PGRES_POLLING_READING

  Async connection is waiting to read

PGRES_POLLING_WRITING

  Async connection is waiting to write

PGRES_SINGLE_TUPLE
PGRES_TUPLES_OK

      Successful completion of a command returning data

  (such as a SELECT or SHOW).

PG_DIAG_COLUMN_NAME

  If the error was associated with a specific table column, the name of the column. (When this field is present, the schema and table name fields identify the table.)

PG_DIAG_CONSTRAINT_NAME

  If the error was associated with a specific constraint, the name of the constraint. The table or domain that the constraint belongs to is reported using the fields listed above. (For this purpose, indexes are treated as constraints, even if they weren't created with constraint syntax.)

PG_DIAG_CONTEXT

  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 rst.

PG_DIAG_DATATYPE_NAME

  If the error was associated with a specific datatype, the name of the datatype. (When this field is present, the schema name field provides the name of the datatype's schema.)

PG_DIAG_INTERNAL_POSITION

  This is dened the same as the PG_DIAG_STATEMENT_POSITION eld, but it is used when the cursor position refers to an internally generated command rather than the one submitted by the client. The PG_DIAG_INTERNAL_QUERY eld will always appear when this eld appears.

PG_DIAG_INTERNAL_QUERY

  The text of a failed internally-generated command. This could be, for example, a SQL query issued by a PL/pgSQL function.

PG_DIAG_MESSAGE_DETAIL

  an optional secondary error message carrying more detail about the problem. Might run to multiple lines.

PG_DIAG_MESSAGE_HINT

  an 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.

PG_DIAG_MESSAGE_PRIMARY

  The primary human-readable error message (typically one line). Always present.

PG_DIAG_SCHEMA_NAME

  If the error was associated with a specific database object, the name of the schema containing that object, if any.

PG_DIAG_SEVERITY

  The severity; 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. Always present.

PG_DIAG_SOURCE_FILE

  The le name of the source-code location where the error was reported.

PG_DIAG_SOURCE_FUNCTION

  The name of the source-code function reporting the error.

PG_DIAG_SOURCE_LINE

  The line number of the source-code location where the error was reported.

PG_DIAG_SQLSTATE

  The SQLSTATE code for the error. The SQLSTATE code identies the type of error that has occurred; it can be used by front-end applications to perform specic operations (such as er- ror handling) in response to a particular database error. For a list of the possible SQLSTATE codes, see Appendix A. This eld is not localizable, and is always present.

PG_DIAG_STATEMENT_POSITION

  A string containing a decimal integer indicating an error cursor position as an index into the original statement string. The rst character has index 1, and positions are measured in characters not bytes.

PG_DIAG_TABLE_NAME

      If the error was associated with a

  specific table, the name of the table. (When this field is present, the schema name

      field provides the name of the table's schema.)

PQERRORS_DEFAULT

  Default error verbosity level (#set_error_verbosity)

PQERRORS_TERSE

  Terse error verbosity level (#set_error_verbosity)

PQERRORS_VERBOSE

  Verbose error verbosity level (#set_error_verbosity)

PQPING_NO_ATTEMPT

  Connection not attempted (bad params).

PQPING_NO_RESPONSE

  Could not establish connection.

PQPING_OK

  Server is accepting connections.

PQPING_REJECT

  Server is alive but rejecting connections.

PQTRANS_ACTIVE

  Transaction is currently active; query has been sent to the server, but not yet completed. (#transaction_status)

PQTRANS_IDLE

  Transaction is currently idle (#transaction_status)

PQTRANS_INERROR

  Transaction is currently idle, in a failed transaction block (#transaction_status)

PQTRANS_INTRANS

  Transaction is currently idle, in a valid transaction block (#transaction_status)

PQTRANS_UNKNOWN

  Transaction's connection is bad (#transaction_status)

SEEK_CUR

  Flag for lo_lseek – seek from current position

SEEK_END

  Flag for lo_lseek – seek from object end

SEEK_SET

  Flag for lo_lseek – seek from object start