On Sun, Feb 14, 2010 at 03:15:30PM -0500, Tom Lane wrote:
> So the currently submitted patch is logically inconsistent. If we
> enforce a character set restriction on the payload for fear of
> being unable to convert it to the destination client_encoding, then
> we should logically do the same for the condition name. But then
> why not also restrict a lot of other things to pure ASCII?
AFAICS this essentially goes for "payload is a text string" and for
people who want "payload as binary" will have to do hex encoding or
some such. At least, I thought one of the reasons why it got limited
was because we couldn't decide.
Have a nice day,
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
In response to
pgsql-hackers by date
|Next:||From: Jeff Davis||Date: 2010-02-15 21:24:37|
|Subject: Re: LISTEN/NOTIFY versus encoding conversion|
|Previous:||From: Federico Di Gregorio||Date: 2010-02-15 20:41:21|
|Subject: Re: psycopg2 license changed|