Documentation

A wrapped PGConnection. This differs from a bare PGConnection in a few ways:

1. It always has exactly one active transaction (with pgBegin)
2. It automatically disconnects on GC
3. It provides a mutex around the underlying PGConnection for thread-safety

Connect to a database for HDBC use (equivalent to pgConnect and pgBegin).

Convert an existing PGConnection to an HDBC-compatible Connection. The caveats under connectionPG apply if you plan to continue using the original PGConnection.

Use the underlying PGConnection directly. You must be careful to ensure that the first invariant is preserved: you should not call pgBegin, pgCommit, or pgRollback on it. All other operations should be safe.

Reload the table of all types from the database. This may be needed if you make structural changes to the database.

Number of rows to fetch (and cache) with execute and each time fetchRow requires more rows. A higher value will result in fewer round-trips to the database but potentially more wasted data. Defaults to 1. 0 means fetch all rows.

Change the connectionFetchSize for new Statements created with prepare. Ideally this could be set with each call to execute and fetchRow, but the HDBC interface provides no way to do this.