public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Pavel Golub <[email protected]>
Cc: [email protected]
Subject: Re: Lack of docs for libpq C Library
Date: Thu, 31 Jan 2008 11:22:17 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Alvaro Herrera <[email protected]> writes:
> I disagree.  I think PQinitSSL is meant to be called from the
> application, for example.  Same with PQsetClientEncoding.  And the
> PQExpBuffer stuff is all very useful, and years ago when I wrote an app
> to use it it annoyed me that there were no docs on it.  (Back then, I
> didn't realize I could have complained about it or written the docs
> myself).

PQinitSSL *is* documented, though looking at the para immediately raises
the question what the heck we are doing pointing to a random hp.com page
for SSL documentation.

PQsetClientEncoding seems to be documented in the wrong place.

As for the expbuffer stuff, that is intentionally not considered part of
libpq's exported API.  If someone uses it, they get to keep both parts
when it breaks.

			regards, tom lane

view thread (25+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Lack of docs for libpq C Library
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox