Re: possible design bug with PQescapeString()

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tatsuo Ishii" <ishii(at)sraoss(dot)co(dot)jp>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: possible design bug with PQescapeString()
Date: 2006-02-26 14:58:29
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0F7EA@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-02-26 16:00:46 Re: TOAST compression
Previous Message Magnus Hagander 2006-02-26 14:40:33 Re: possible design bug with PQescapeString()