Regarding the checkin comment from the fix for ticket 1654:
Always register BINARY collating sequences for UTF-16BE and
UTF-16LE both. Formerly we were only registering the native byte
order by default. Ticket #1654 . Note: There may still be problems
with collating sequence synthesis. (By drh)
Does this mean this specific problem is solved, but other similar
problems may still exist and they just didn't surface with this
specific database?
What exactly is the "collating sequence synthesis"?
And what was the trigger for the crash? Was it the use of ALTER
TABLE, or was it just related to UTF-16BE/UTF-16LE?
Thanks,
</jum>
