| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 19:18:55 |
| Message-ID: | 200404132118.55010.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> 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.
Like what? I think it could be fairly useful. We would have to
restrict ourselves to character sets that are supersets of ASCII, but
there are boatloads of reasons to do that besides this issue.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2004-04-13 19:21:57 | Re: Lexing with different charsets |
| Previous Message | Tom Lane | 2004-04-13 19:18:42 | Re: query slows down with more accurate stats |