|
When an application is converted to use Unicode data in the database, is it necessary to change the collation algorithm to UCA? http://dcx.sybase.com/index.html#1201/en/sachanges/unloading-reloading-upgrading-newjasper.html |
|
AFAIK (but John will know faaaaar better), unicode data will use the UCA collation by default, cf. this quote from the DBINIT docs:
So I would conclude that you would not have to change the default collation for (non-unicode) char data. More directly, UCA is not required to use Unicode in the database: you can also use UTF8BIN. The primary difference is in how values sort & compare. For example, you cannot even do accent-insensitve comparisons with UTF8BIN let alone complex linguistically correct sorting.
(12 Apr '11, 21:27)
John Smirnios
@Volker: UCA is the default for -zn, which does not apply in this case because the database has no NCHAR columns. I think dbinit -z is more pertinent in my case.
(13 Apr '11, 12:59)
Breck Carter
Replies hidden
How do you use unicode data when not using NCHAR columns? - Does it mwan you just want to use a linguistically correct collation but store narrow chars? (If so, I misunderstood your requirements...)
(13 Apr '11, 13:01)
Volker Barth
|
