Breaking changes
Product feature changes that create incompatibilities with previous versions
Table 1. Breaking changes listed by the version each change was implemented
Version implemented | Description | Recommendations |
---|---|---|
13.0.3 | ctChecklock is now enabled on all files by default, so we do not allow a connection to update a record if it has not been locked (the attempt will fail with error 57). This safeguards against potential crashes/hangs when freeing unclaimed locks. | If you wish to restore the old behavior of allowing updates on records that are not locked, set AUTO_CHECKLOCK to NO. |
13.0.3 | Previously, when using ctdbSetBatchFilter to add a record filter to a batch, the filter could be applied to other record handles you used while the batch was active. Now, the filter will apply only to the record that the batch refers to. | If you relied on the old behavior, please contact FairCom Support. |