[CAY-2019] Optimistic locking always fails on CRYPTO columns

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0.M2
• Fix Version/s: 4.2.M1
• Component/s: Core Library
• Assignee: John Huss
• Reporter: John Huss
• Created: 29/Jun/15 20:37
• Updated: 15/Jul/19 14:29
• Resolved: 15/Jul/19 14:29

Description

If you have optimistic locking turned on for columns that are configured to be encrypted (named CRYPTO_*) then updates to those rows will always fail because it uses the unencrypted value to check the optimistic locking, ie. WHERE encryptedColumn = <unencryptedValue>

Issue Links

• links to: GitHub Pull Request #397
• links to: GitHub Pull Request #398