From: Schroeder, Alexander (alexander.schroedersap.com)
Date: Mon Dec 27 2004 - 09:14:40 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello Jaroslaw,

You may want to define and use a MAPCHAR set (http://dev.mysql.com/doc/maxdb/en/48/8f3144ba9511d2a97100a0c9449261/content.htm)
and then use the MAPCHAR function in your query (http://dev.mysql.com/doc/maxdb/en/27/d83c3eba7411d2a97100a0c9449261/content.htm).

UNICODE uses the raw UNICODE (strictly speaking the UCS-2) order of the characters, which is possibly also not what you want - you probably
want a lexicographical sort order with umlauts/accented letters sorted after/like their unaccented counterparts - that can be defined using a
MAPCHAR set.

Regards
Alexander Schröder
SAP DB, SAP Labs Berlin

> -----Original Message-----
> From: Jaros³aw Szczepankiewicz [mailto:jarrmanpoczta.onet.pl]
> Sent: Monday, December 27, 2004 3:21 PM
> To: maxdblists.mysql.com
> Subject: ISO-8859-2 and ORDER BY
>
> Hi,
>
> is there any possibility to force SAP DB/MAX DB to treat data
> in iso-8859-2
> or windows-cp1250 correctly with ORDER BY operations? What if
> I use UNICODE
> while creating database, would it fit for my needs? Is there
> any option to
> do it without making UNICODE database (larger volume size).
> Thanks for any
> help.
>
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe:
> http://lists.mysql.com/maxdb?unsub=alexander.schroedersap.com
>
>
>

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]