Re: Lexing with different charsets - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Lexing with different charsets
Date
Msg-id 25666.1081884747@sss.pgh.pa.us
Whole thread Raw
In response to Re: Lexing with different charsets  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane wrote:
>> 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?

The first things that came to mind were losing psql's ability to tell
what's a literal, losing the existing capability for queries to be
translated from client-side to server-side character set, and losing the
capability to have character sets defined by plug-in extensions rather
than being hard-wired into the lexer.  (Before you claim that the last
is easily solved, consider that the lexer is not allowed to do database
accesses.)

> 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.

If we do that then some of the problems go away, but I'm not sure they
all do.  Are you willing to drop support for non-ASCII-superset
character sets on the client side as well as the server?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Lexing with different charsets
Next
From: Tom Lane
Date:
Subject: Re: FRONTEND in ecpg