You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using ConditionalVersionField for a model, specifically with ignore_fields configured in my ConcurrencyMeta. I'm finding that, when multiple instances of the class are loaded simultaneously, the initial is being shared/overwritten rather than being uniquely maintained per instance, thus leading to significantly more version bumps (and RecordModifiedErrors) than expected
In my observations, the models are loaded and the initial is recorded in _concurrencymeta at
. However, the ._concurrencymeta actually appears to be shared across all my instances, meaning that each loaded instance overwrites the recorded initial value for preceding instances. When it's consulted to check for changes (
What's the recommended process to contribute? I tried pushing a branch in order to open a PR, but was denied access; do you recommend forking or something like that?
I'm using
ConditionalVersionField
for a model, specifically withignore_fields
configured in myConcurrencyMeta
. I'm finding that, when multiple instances of the class are loaded simultaneously, theinitial
is being shared/overwritten rather than being uniquely maintained per instance, thus leading to significantly more version bumps (andRecordModifiedError
s) than expectedIn my observations, the models are loaded and the
initial
is recorded in_concurrencymeta
atdjango-concurrency/src/concurrency/fields.py
Line 335 in b915a3c
._concurrencymeta
actually appears to be shared across all my instances, meaning that each loaded instance overwrites the recordedinitial
value for preceding instances. When it's consulted to check for changes (django-concurrency/src/concurrency/fields.py
Lines 370 to 373 in b915a3c
The text was updated successfully, but these errors were encountered: