Got a link to that section of the standard, or better yet, to a 'interpreted' version of the standard? :-)
Stephan Szabo wrote:
> On Wed, 13 Aug 2003, Dennis Gearon wrote:
>
>
>>Dennis Bj?rklund wrote:
>>
>>
>>>In the future we need indexes that depend on the locale (and a lot of other changes).
>>>
>>
>>I agree. I've been looking at the web on this subject a lot lately. I
>>am **NOT** a microslop fan, but SQL-SERVER even lets a user define a
>>language(maybe encoding) down to the column level!
>>
>>I've been reading on GNU-C and on languages, encoding, and localization.
>>
>>http://pauillac.inria.fr/~lang/hotlist/free/licence/fsf96/drepper/paper-1.html
>>http://h21007.www2.hp.com/dspp/tech/tech_TechSingleTipDetailPage_IDX/1,2366,1222,00.html
>>
>>
>>There are three basic approaches to doing different langauges in computerized text:
>>
>> A/ various adaptations of the 8 bit character set, I.E. the ISO-8859-x series.
>> B/ wide characters
>> ********This should be how Postgress stores data internally.********
>> C/ Multibyte characters
>> ********This is how Postgress should default to sending data OUT of the application,
>> i.e. to the display or the web, or other system applications********
>
>
> SQL has a system for defining character set specifications, collations and
> such (per column/literal in some cases). We should probably look at it
> before making decisions on how to do things.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
