Hello Ruth, > Just a heads up for the developers/documentation developers. > I did some > googling on MaxDB + MAPCHAR in UNICODE databases and found many > references on the mailing list (from Elke) indicating that this is > basically not supported. I wanted to point out a > documentation link that > disagrees: > > http://www.sapdb.org/7.4/htmhelp/be/a51a26c6cf11d5993e00508b6b > 8b11/frameset.htm
Thank you for pointing this out, it seems to be wrong ... > Or, at least it seems to disagree to me. I did verify, > however, that in > the DB Manager GUI, I cannot create a UNICODE MAPCHAR definition > (unfortunately). > > I looked into this because we have an application that is displaying > German cities and �ttingen is being displayed at the very end of the > list, because the column is (and needs to be) UNICODE. > > It would certainly be nice to be able to address this > efficiently at the > DB level, w/o needing to add sort logic to the application. Unfortunately, MaxDB does not support a feature known as 'collations', and will not support it in the foreseeable future. Anyway for only german umlauts you may want to go with ASCII columns, and possibly a MAPCHAR set, as almost everything that you need is in the first 255 chars of Unicode (except, unfortunately, the Euro currency sign). Regards Alexander Schr�der SAP DB, SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
