[GemStone-Smalltalk] Caveats on Switching to Unicode Comparison Mode

[Richard Sargent via GemStone-Smalltalk]

Upgrading an existing GemStone database to use Unicode requires careful
planning and execution. There are significant differences from conventional
strings that affect how strings (Unicode or traditional) sort and compare.
[*Note that installing Seaside in an existing GemStone database will upgrade
it to Unicode*.]

The bug note for issue  #46694
<https://gemtalksystems.com/data/bugnotes/46694.html>   addresses some of
these.
"When changing an existing application from the standard mode to Unicode
Comparison Mode, you must take steps to ensure any structures relying on
comparisons are rebuilt; indexes on strings must be rebuilt, sorted
collections on strings may need to be re-sorted, and dictionaries with
string keys may need to be rebuilt."

Chapters 5 and 7 of the  3.3 Programming Guide
<https://downloads.gemtalksystems.com/docs/GemStone64/3.3.x/GS64-ProgGuide-3.3.pdf>  
discuss Unicode in the context of strings and of indexes.






--
View this message in context: http://forum.world.st/Caveats-on-Switching-to-Unicode-Comparison-Mode-tp4937938.html
Sent from the Gemstone/S mailing list archive at Nabble.com.