Re: possible design bug with PQescapeString() - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: possible design bug with PQescapeString()
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0F7EA@algol.sollentuna.se
Whole thread Raw
In response to possible design bug with PQescapeString()  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-hackers
> > > > > Sound good to pass PGconn to new-PQescapeString. Here is the
> > > > > proposed calling sequence for the new function:
> > > > >
> > > > > size_t PQescapeStringWithConn (const PGconn *conn, char
> > > *to, const
> > > > > char *from, size_t length)
> > > > >
> > > > > If this is ok, I will implement for 8.2.
> > >
> > > Here is the promised patches for 8.2. If there's no objection, I
> > > will commit tomorrow.
> >
> > Just a reminder - to work on win32, the new function needs
> an entry in
> > exports.txt.
>
> Thanks. Could you tell me what the number column in the file
> is? Can I assign arbitary number for the function? (maybe
> next to the last
> number?) I'm not familiar with win32 build.

It just has to be unique, and never change for each function. So just
assign the next one in sequence.

//Magnus


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: possible design bug with PQescapeString()
Next
From: "Jim C. Nasby"
Date:
Subject: Re: TOAST compression