Next: Query Construction, Previous: Miscellaneous, Up: Top
This chapter lists libpq interface elements that are not
provided by module (database postgres) and explains why they are
omitted.
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.
Laziness, pure and simple.
More laziness. Since we have
pg-reset, we have the proper mechanism for dealing withPQstatusvalues other thanCONNECTION_OK.
Unlikely to be useful.
PostgreSQL documentation says:
This function is deprecated in favor of PQoidValue. It is not thread-safe.
Deprecated in favor of
PQescapeStringConnandPQescapeByteaConn, respectively.
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.
We provide the schemefied interface
pg-set-notice-out!.
These “really old printing routines” are obsoleted by
pg-print.
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 fromgetenvdirectly). For example:(and=> (getenv "PGCLIENTENCODING") pg-set-client-encoding!)See Database Connections.