From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Lexing with different charsets |
Date: | 2004-04-13 18:27:29 |
Message-ID: | 25016.1081880849@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> writes:
> My next question is about lexing. The spec says that one can use strings
> of different charsets in the queries, like:
> ... WHERE field1 = _latin1'FooBar' and field2 = _utf8''
> I can see that the lexer either needs to be taught about all the
> different charsets or this is not going to work very well.
Yeah. I'm not sure that we're ever going to support that part of the
spec; doing so would break too many useful things without adding very
much useful functionality.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2004-04-13 18:35:39 | Join works in 7.3.6, fails in 7.4.2 |
Previous Message | Thomas Swan | 2004-04-13 18:23:38 | Re: rotatelogs integration in pg_ctl |