Merlin Moncure <mmoncure@gmail.com> writes:
> On Fri, Jan 8, 2010 at 1:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> No, he meant ASCII. �Otherwise we're going to have to deal with encoding
>> conversion issues.
> That seems pretty awkward...instead of forcing an ancient, useless to
> 90% of the world encoding, why not send bytea
You mean declare the notify parameter as bytea instead of text, and dump
all encoding conversion issues onto the user? We could do that I guess.
I'm not convinced that it's either more functional or more convenient to
use than a parameter that's declared as text and restricted to ASCII.
> If we must use ascii, we should probably offer conversion functions
> to/from text, right?
There's encode() and decode(), which is what people would wind up using
quite a lot of the time if we declare the parameter to be bytea.
regards, tom lane
