Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Sun, 26 Feb 2006 15:58:29 +0100
  • Message-id: <6BCB9D8A16AC4241919521715F4D8BCEA0F7EA(at)algol(dot)sollentuna(dot)se>

> > > > > 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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group