|
|
|
While opening a Unicode table, the logic looks for KSEG definitions at the table level, index level, and segment level. For a table with multiple indexes and multiple segments per index, this results in a large number of client/server calls. The logic has been refined to reduce the number of calls required.
The kseg* element names in the CTDBTABLE and CTDBINDX structures have been changed to unicode_kseg* to clarify their meaning. It is not expected for applications to be accessing these member elements directly, so this should be a benign change.
Note: This is a Compatibility Change when accessing these members directly using c-treeDB and Unicode.
