cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Huss (JIRA)" <>
Subject [jira] [Commented] (CAY-2019) Optimistic locking always fails on CRYPTO columns
Date Tue, 09 Jul 2019 14:44:00 GMT


John Huss commented on CAY-2019:

My thought here was just to turn off optimistic locking in the runtime for these columns so
at least you can still function.

But an additional step would be to add a warning to modeler to tell the user to uncheck locking
for these columns. We'd have to just assume which ones are crypto columns using the default
configuration, i.e. starts with "CRYPTO_", however I'd like to make the comparison case insensitive
if possible because my columns have this all in lowercase.

> Optimistic locking always fails on CRYPTO columns
> -------------------------------------------------
>                 Key: CAY-2019
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 4.0.M2
>            Reporter: John Huss
>            Assignee: John Huss
>            Priority: Minor
> 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>

This message was sent by Atlassian JIRA

View raw message