| From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Lexing with different charsets |
| Date: | 2004-04-13 19:21:57 |
| Message-ID: | Pine.LNX.4.44.0404132117410.4551-100000@zigo.dhs.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 13 Apr 2004, Tom Lane wrote:
> We could possibly do it if we restrict to ASCII-superset character sets
> (not UTF-16 for instance), so that the string quoting boundaries can be
> found without hardwired knowledge about every character set.
It's a reasonable compromise I guess. One can still support utf-16 and
others using the new wire protocol and maybe with some escaping extension
like:
_utf16 H'a42a1121311'
where H would be a way to form a string from hexencoded bytes (or
using the same as for bytea, or whatever). It's a problem for the future.
--
/Dennis Björklund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-13 19:32:27 | Re: Lexing with different charsets |
| Previous Message | Peter Eisentraut | 2004-04-13 19:18:55 | Re: Lexing with different charsets |