#30557: Using Query Expression for ordering in multi-table inheritance scenario
triggers TypeError during test
-------------------------------------+-------------------------------------
Reporter: Jonny | Owner: nobody
Fuller |
Type: Bug | Status: new
Component: Database | Version: 2.2
layer (models, ORM) |
Severity: Normal | Keywords: ordering
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi friends,
During testing I discovered a strange bug when using a query expression
for ordering during multi-table inheritance. You can find the full write
up as well as reproducible test repository
[here](https://github.com/JonnyWaffles/djangoordermetabug). The bug occurs
because the field is an OrderBy object, not a string, during
get_order_dir. The linked stacktrace should make the issue obvious, but
what I don't understand is why it only fails during test db setup, not
during repl or script use. I wish I could help more and come up with a
real solution. Hopefully, this is enough for someone wiser to find the
culprit.
--
Ticket URL: <https://code.djangoproject.com/ticket/30557>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/055.44c30a904a9135816231ce85de00e1c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
