[Glass] Conflicts when using *String and Unicode* based indexes in GemStone 3.2 and Seaside

Dale Henrichs dale.henrichs at gemtalksystems.com
Wed Jul 2 14:35:53 PDT 2014

In 3.2 the  offsets for the System class>>_sessionStateAt:put: family of
methods were changed at the system level (a new block of gemstone private
session state offsets was allocated) without changing the corresponding
offsets in the  System class>>_sessionStateAt:put: methods.

Seaside uses _sessionStateAt:put: to count the number of requests handled
among other things and it turns out that the range used by Seaside happens
to overlap the session state used by Unicode16 class>>usingUnicodeCompares
(which is used to indicate whether or not unicode compare mode is in effect
or not).

The #usingUnicodeCompares method  is used by the indexing subsystem to
determine whether or not Strings are allowed to be used in Unicode indexes
or not ...

Soooo, I will be pushing out a new fix for Seaside3 ... probably
with a fix for this bug[1] and a couple of other bugfixes[2] that were
queued up (known bugfixes). If there is a bugfix for Seaside3.1 that you've
been waiting on that's not on the list[2], now is a good time to bring it
to my attention.


[1] https://github.com/glassdb/Seaside31/issues/29
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140702/2d9c268f/attachment.html>

More information about the Glass mailing list