Hi,
as a workaround, I added an additional column (aka CharField) to store the
hash of that JSON string. Then only the hashes have to be compared. Sure,
this is not an elegant solution, as it adds redundant data to your database.
If I would write SQL by hand, I could compare the JSON-string usin
I'm guessing it's got to do with testing for equality. It will be
restricted to how the field prepares data for querying the database, and
(speaking as the maintainer of JSONField) you need to be very careful with
querying on json fields, as the data is stored as a string, so changes
about how
2 matches
Mail list logo
