#34013: order_by() crashes with annotated JSONObject fields.
-------------------------------------+-------------------------------------
Reporter: Eugene Morozov | Owner: Aman
| Pandey
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: orm, json, ordering | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by saadullahaleem):
Replying to [comment:9 Eugene Morozov]:
> I haven't tested this problem with the latest versions of Django 4.2 and
postgres 3. Nonetheless, I don't believe that the issue is linked to the
modifications made in Django 4.2.
>
> So, you can try to run the code from the example and I think it will be
still not working.
>
Thanks for the quick response.
I was able to reproduce it on the main branch but to fix it, a model would
need to be attached to the JSONField inside the JSONObject method but it
can't be done since annotations don't modify the class itself. So it seems
like it might require a big architectural change for this to work.
--
Ticket URL: <https://code.djangoproject.com/ticket/34013#comment:10>
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/01070187d1ef1fd3-534a2922-94eb-41c3-bc7d-f989ebce05ae-000000%40eu-central-1.amazonses.com.
