| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Marko Kreen" <markokr(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>,"Sam Mason" <sam(at)samason(dot)me(dot)uk> |
| Subject: | Re: [rfc] unicode escapes for extended strings |
| Date: | 2009-04-17 22:19:52 |
| Message-ID: | 49E8BA37.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The lexer is *not* allowed to invoke any database operations
> (such as pg_conversion lookups)
I certainly hope it's not!
> so it cannot perform arbitrary encoding conversions.
I was more questioning whether we should be looking at character
encodings at all at that point, rather than suggesting conversions
between different ones. If committing the escape sequence to a
particular encoding is unavoidable at that point, then I suppose the
code in question is about as good as it gets.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Jaskiewicz | 2009-04-17 23:39:41 | Re: [GENERAL] Performance of full outer join in 8.3 |
| Previous Message | Marko Kreen | 2009-04-17 21:55:33 | Re: [rfc] unicode escapes for extended strings |