Re: [HACKERS] PQescapeIdentifier

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] PQescapeIdentifier
Date: 2006-07-03 03:29:19
Message-ID: 22562.1151897359@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Hang on a second. Has someone considered the encoding issues this might
> suffer from, same as PQescapeString?

That was the point I raised when I saw the commit.

My advice is we shouldn't have PQescapeIdentifier at all.
PQescapeIdentifierConn would be the thing to define,
parallel to PQescapeStringConn.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-07-03 03:43:47 Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)
Previous Message Tom Lane 2006-07-03 03:21:45 Re: table/index fillfactor control, try 3

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-07-03 03:43:47 Re: ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)
Previous Message Tom Lane 2006-07-03 03:21:45 Re: table/index fillfactor control, try 3