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 have problem by models that defined a clustering-key as get_pk_field in Meta class, Suppose a model by repetitious partition-key that first clustering-key is unique UUID, when i defined model partition-key as get_pk_field on the admin panel when i click on the item MultipleObjectsReturned error raising, and when i set clustering-key as get_pk_field, in results of queries partition-key value is equal to clustering key but in keyspace table these values are distinct.
The text was updated successfully, but these errors were encountered:
mohsenjavidpanah
changed the title
The Django-Admin raise error by non partition-key "get_pk_field"
The Django present BUG by non partition-key "get_pk_field"
Apr 30, 2018
mohsenjavidpanah
changed the title
The Django present BUG by non partition-key "get_pk_field"
Django present BUG by non partition-key "get_pk_field"
May 1, 2018
I have been observed this behaviour. The objects retrieved with .get (anyprimarykey=x) result in wrong partition key assignment, which copies the searched primary key value, and the real partition key value is missing from the object. This is a big issue with get clauses. It doesn`t happen with filter.
Hi guys
I have problem by models that defined a clustering-key as
get_pk_field
in Meta class, Suppose a model by repetitious partition-key that first clustering-key is unique UUID, when i defined model partition-key asget_pk_field
on the admin panel when i click on the itemMultipleObjectsReturned
error raising, and when i set clustering-key asget_pk_field
, in results of queries partition-key value is equal to clustering key but in keyspace table these values are distinct.The text was updated successfully, but these errors were encountered: