Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PQescapeIdentifier
- From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
- To: "Christopher Kings-Lynne" <chris(dot)kings-lynne(at)calorieking(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: PQescapeIdentifier
- Date: Wed, 31 May 2006 08:28:47 +0100
> -----Original Message----- > From: pgsql-hackers-owner(at)postgresql(dot)org > [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of > Christopher Kings-Lynne > Sent: 31 May 2006 04:16 > To: Tom Lane > Cc: Hackers > Subject: Re: [HACKERS] PQescapeIdentifier > > > Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> writes: > >> Here's a question. I wish to add a function to libpq to escape > >> PostgreSQL identifiers. Will this function be subject to the same > >> security/encoding issues as PQescapeString? > > > > Is this of any general-purpose use? How many apps are > really prepared > > to let an untrusted user dictate which columns are > selected/compared? > > phpPgAdmin has use for it, I assume pgAdmin would as well. Yes, it would. Regards, Dave.
- Prev by Date: Re: plperl's ppport.h out of date?
- Next by Date: Re: [PATCHES] Magic block for modules
- Previous by thread: Re: PQescapeIdentifier
- Next by thread: LinkedIn
- Indexes: