---

8 Not Included

This chapter lists libpq interface elements that are not provided by module (database postgres) and explains why they are omitted.

C Macro: PQsetdb ¶

PostgreSQL documentation says:

It is provided for backward compatibility with very old programs.

Since no one has asked for it in Guile-PG, we assume no such programs exist.

C Function: PQconnectStart ¶

C Function: PQconnectPoll ¶

C Function: PQresetStart ¶

C Function: PQresetPoll ¶

Laziness, pure and simple.

C Function: PQstatus ¶

More laziness. Since we have pg-reset, we have the proper mechanism for dealing with PQstatus values other than CONNECTION_OK.

C Function: PQsocket ¶

Unlikely to be useful.

C Function: PQgetssl ¶

We’ll get to SSL support one of these days.

C Function: PQresStatus ¶

C Function: PQclear ¶

C Function: PQmakeEmptyPGresult ¶

C Function: PQcmdStatus ¶

Unlikely to be useful.

C Function: PQoidStatus ¶

PostgreSQL documentation says:

This function is deprecated in favor of PQoidValue. It is not thread-safe.

C Function: PQescapeString ¶

C Function: PQescapeBytea ¶

Deprecated in favor of PQescapeStringConn and PQescapeByteaConn, respectively.

C Function: PQfreemem ¶

Internal.

C Function: PQfn ¶

PostgreSQL documentation says:

Tip: This interface is somewhat obsolete, as one may achieve similar performance and greater functionality by setting up a prepared statement to define the function call. Then, executing the statement with binary transmission of parameters and results substitutes for a fast-path function call.

C Function: PQputnbytes ¶

C Function: PQputline ¶

C Function: PQgetline ¶

C Function: PQgetlineAsync ¶

C Function: PQendcopy ¶

These are in the section “Obsolete Functions for COPY”.

C Function: PQsetNoticeReceiver ¶

C Function: PQsetNoticeProcessor ¶

We provide the schemefied interface pg-set-notice-out!.

C Function: PQdisplayTuples ¶

C Function: PQprintTuples ¶

These “really old printing routines” are obsoleted by pg-print.

C Function: PQenv2encoding ¶

This function does (getenv "PGCLIENTENCODING") and returns the numeric value of the result, which is not useful, since Guile-PG uses a string to describe the client encoding (you can use the value from getenv directly). For example:

(and=> (getenv "PGCLIENTENCODING")
       pg-set-client-encoding!)

See Procedures for managing connections.