Re: PQexecParams

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQexecParams
Date: 2005-03-16 15:59:18
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A7649@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> >> Even binary data? ie. You could upload a binary string straight
into
> >> PQexecParams with no octal conversion?
>
> > Well, what it means you do not have to escape data at the protocol
level
> > you don't have to be concerned about formatting the query string.
> > However the server still may still need to interpret the data for
> > storage...meaning for the bytea type at least you have to do octal
> > encoding (at least that's what I do, I'd like nothing better than to
be
> > corrected on this point).
>
> Not if you send the bytea parameter in binary format. If you send it
in
> text format that's true.

Whoops! In fact, my ISAM driver does exactly this. However, it is
still interpreting octal codes returned from the server. This is
because liqpq's restriction to ask for the result in all text/all
binary. However IIRC this is not a restriction of the protocol.

Merlin

Browse pgsql-hackers by date

  From Date Subject
Next Message David Pradier 2005-03-16 16:14:32 Re: Erratic error message "ERROR: column "id_compte" does
Previous Message Moran.Michael 2005-03-16 15:46:23 contrib/pgcrypto