On 2007-04-04, Alvaro Herrera <[EMAIL PROTECTED]> wrote: > Right -- IMHO what we should be doing is reject any input to chr() which > is beyond plain ASCII (or maybe > 255), and create a separate function > (unicode_char() sounds good) to get an Unicode character from a code > point, converted to the local client_encoding per conversion_procs.
Thinking about this made me realize that there's another, ahem, elephant in the room here: convert(). By definition convert() returns text strings which are not valid in the server encoding. How can this be addressed? -- Andrew, Supernews http://www.supernews.com - individual and corporate NNTP services ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
