Re: UTF-8 context of BYTEA datatype??

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: UTF-8 context of BYTEA datatype??
Date: 2006-05-31 10:29:21
Message-ID: 20060531102921.GE23169@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, May 31, 2006 at 11:31:28AM +0200, Daniel Verite wrote:
> Martijn van Oosterhout wrote:
>
> > However, there is a solution: send the paramters seperate from the
> > query. In fact, postgres has been able to do that for a while now but
> > not all interfaces have been made to use it. My guess is that those
> > other databases you've used were already doing this so didn't see the
> > issue. I don't know if DBD:Pg does this though, maybe it needs to be
> > triggered somehow.
>
> Actually, this is the case already. When a parameter is explicitly
> typed as bytea, then libpq's PQexecPrepared is used and the binary
> contents are passed outside of the query.

Why isn't PQexecPrepared always used? And why does typing it SQL_BINARY
not do the same?

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tino Wildenhain 2006-05-31 10:34:11 Re: Best high availability solution ?
Previous Message Arnaud Lesauvage 2006-05-31 10:27:29 Re: Best high availability solution ?