Re: [rfc] unicode escapes for extended strings - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [rfc] unicode escapes for extended strings
Date
Msg-id 49E8D87A.6080607@dunslane.net
Whole thread Raw
In response to Re: [rfc] unicode escapes for extended strings  (Marko Kreen <markokr@gmail.com>)
Responses Re: [rfc] unicode escapes for extended strings  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers

Marko Kreen wrote:
> +    if (c > 0x7F)
> +    {
> +        if (GetDatabaseEncoding() != PG_UTF8)
> +            yyerror("Unicode escape values cannot be used for code point values above 007F when the server encoding
isnot UTF8");
 
> +        saw_high_bit = true;
> +    }
>   

Is that really what we want to do? ISTM that one of the uses of this is 
to say "store the character that corresponds to this Unicode code point 
in whatever the database encoding is", so that \u00a9 would become an 
encoding independent way of designating the copyright symbol, for instance.

cheers

andrew




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Replacing plpgsql's lexer
Next
From: "Kevin Grittner"
Date:
Subject: Re: [rfc] unicode escapes for extended strings