#34397: Subclasses of JSONField call `get_prep_value` with field as value
-------------------------------------+-------------------------------------
Reporter: pheki | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Julie Rymer):
This issue was filed for django 3.2 so the recent change in `JSONField`
behaviour has no impact.
However, from what I understand @pheki, wants two different behaviour
depending on the field it is called on. For that the solution is to create
two custom classes, each implementing the behaviour that you want and
assign it to the corresponding field.
--
Ticket URL: <https://code.djangoproject.com/ticket/34397#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187e61a1c85-04a5ad67-ee66-4a68-b1a6-c1f5404d04bc-000000%40eu-central-1.amazonses.com.
