DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=P8B5DBjTiWHcWA7uuvGKTBTt9zfsoofL/fZrXa5QSimfF2J39if+7GxNnJ+mmA2K1I62AqDA6sTNf1OynYzC+z/qoeJcTR1NvZCUX6B4atbxSIwsJ0NsROKajR3CvyjDchV3pe6fAmNni+sbFShZ9M5/3QA0RhVMV1DEwj0Gjhs=
Message-ID: <7104a7370506030943662e4be@mail.gmail.com>
Date: Fri, 3 Jun 2005 19:43:34 +0300
From: Volkan YAZICI <volkan.yazici@gmail.com>
Reply-To: Volkan YAZICI <volkan.yazici@gmail.com>
To: David Hinkle <drachs@gmail.com>
Subject: Re: libpq, PQExecParams and the inserting of binary data
Cc: pgsql-interfaces@postgresql.org
In-Reply-To: <ae830e6c05060309182201f85b@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <ae830e6c05060309182201f85b@mail.gmail.com>

Hi,

On 6/3/05, David Hinkle <drachs@gmail.com> wrote:
> As you can see, I assumed I could use PQexapeBytea to escape the
> binary data and then just use the returned value as a text parameter.

You don't need to (also you shouldn't) escape any data while using
parameters. Because, you'll miss one big advantage of parameter usage.
From PQexecParams() documentation:

=ABThe primary advantage of PQexecParams over PQexec is that parameter
values may be separated from the command string, thus avoiding the
need for tedious and error-prone quoting and escaping. Unlike PQexec,
PQexecParams allows at most one SQL command in the given string.
(There can be semicolons in it, but not more than one nonempty
command.) This is a limitation of the underlying protocol, but has
some usefulness as an extra defense against SQL-injection attacks.=BB

Regards.