libecpg library primarily
contains “hidden” functions that are used to
implement the functionality expressed by the embedded SQL
commands. But there are some functions that can usefully be
called directly. Note that this makes your code unportable.
ECPGdebug(int turns on
debug logging if called with the first argument non-zero.
Debug logging is done on
on, FILE *
stream. The log contains
all SQL statements with
all the input variables inserted, and the results from the
PostgreSQL server. This
can be very useful when searching for errors in your
On Windows, if the ecpg libraries and an application
are compiled with different flags, this function call
will crash the application because the internal
representation of the
pointers differ. Specifically,
multithreaded/single-threaded, release/debug, and
static/dynamic flags should be the same for the library
and all applications using that library.
returns the library database connection handle identified
by the given name. If
connection_name is set to
NULL, the current connection
handle is returned. If no connection handle can be
identified, the function returns
NULL. The returned connection handle can
be used to call any other functions from libpq, if necessary.
It is a bad idea to manipulate database connection handles made from ecpg directly with libpq routines.
returns the current transaction status of the given
connection identified by
PQtransactionStatus() for details about
the returned status codes.
returns true if you are connected to a database and false
lineno, const char*
connection_name can be
NULL if a single connection is
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.