#24142: extra() field overwritten when using union on two querysets
-------------------------------------+-------------------------------------
Reporter: dryice | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
Maybe it can be fixed, but the latest thinking I've heard is that we're
trying to make the functionality of `extra()` available through better
APIs so we can deprecate it, so please don't be surprised if this gets a
"won't fix".
--
Ticket URL: <https://code.djangoproject.com/ticket/24142#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.713006136985735ca4b1cf6b081499bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
