Hi
I have been using PQprepare() and PQexecPrepared(). This has led me to
update libpq.sgml, in particular for PQexecParams().
The changes are to the formatting of the arguments for PQexecParams()
(as shared by PQexecPrepared()) which make it easier to read, as well as
creating a table giving a
On Thu, 2006-11-09 at 06:43 -0800, David Fetter wrote:
> On Wed, Nov 08, 2006 at 08:07:19PM +0200, Theo Kramer wrote:
> > Hi
> >
> > I have been using PQprepare() and PQexecPrepared(). This has led me to
> > update libpq.sgml, in particular for PQexecParams().
>
On Fri, 2006-11-10 at 10:50 +0100, Peter Eisentraut wrote:
> Am Donnerstag, 9. November 2006 16:04 schrieb Theo Kramer:
> > Thanks - attached output of 'diff -c libpq.sgml libpq.sgml.org' where
> > libpq.sgml contains my proposed changes and libpq.sgml.org originate
On Fri, 2006-11-10 at 17:24 -0500, Tom Lane wrote:
> Theo Kramer <[EMAIL PROTECTED]> writes:
> > On Fri, 2006-11-10 at 10:50 +0100, Peter Eisentraut wrote:
> >> The patch is backwards.
>
> > Thanks - re-done and re-attached
>
> I applied the part of this t
On Fri, 2006-12-08 at 13:26 -0800, Joshua D. Drake wrote:
> Yes which is generated from our use of SGML which is the core of this
> problem and the core of the question as a whole.
>
> SGML is making working with the documentation *harder*.
>From a total outsider's point of view I have to disagr
Could I venture ...
On Wed, 2007-02-21 at 11:08 -0500, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian wrote:
> > > OK, the FAQ now has:
> > >
> > > The PostgreSQL team makes only bug fixes in minor releases,
> >
> > I don't think there is a causality between the above and th
On Sat, Nov 17, 2007 at 04:05:50PM -0500, Bruce Momjian wrote:
> What I have done is to move the item up to the top of our
> incompatibilities list in the release notes. That is near zero cost for
> everyone.
It bit me when testing my code against PG 8.3. Your docs helped me see my
mistake immedi
On Thu, 2008-03-06 at 01:25 -0500, Tom Lane wrote:
> Greg Smith <[EMAIL PROTECTED]> writes:
> > I think it's funny to consider a specific recommendation for SQLite as
> > being out of line when you look at the history here. The whole reason
> > that software even exists is because of the difficu
