This content has been marked as final. Show 17 replies
Dane and others,
We just finished a couple weeks of work fixing a problem where after a transaction abort, the wrong key could be returned when a key comparator was used that doesn't compare all bytes:
Re: Transaction abort after "replacing" a record in a sorted duplicate DB
After doing these fixes, the major obstacles were removed that were preventing us from making Cursor.putCurrent able to change the data in a duplicates database, when a custom duplicate comparator is used that doesn't compare all bytes. So we went ahead and finished that work, and putCurrent now allows changing the duplicate data.
The change log is below. If you have a need for this prior to the next patch release (currently not scheduled), please send email as usual -- mark.hayes.
Restore a previously disabled feature where Cursor.putCurrent can be used to change the--mark
data for a record in a duplicates database, if a custom duplicate comparator is configured
that does not compare all bytes of the data. This feature was previously disabled in 3.2.28
(see [#15527]) to prevent data corruption. The data corruption issues have been fixed and the
feature is now enabled. [#15704]