#35830: Queryset Union doesn't persist column names
-------------------------------------+-------------------------------------
     Reporter:  Paul Landon Tuckett  |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  4.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  orm, database,       |             Triage Stage:
  queryset, union, sql               |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):

 Hello Paul.

 If you could provide a set of models and a queryset that reproduces it
 would be easier to bisect the changeset that caused it and determine if it
 was intended or not. I suspect this was a necessary change to address an
 issue when combining querysets mixing different field names but it's hard
 to tell for sure without a way to reproduce what you are experiencing.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35830#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701927897b3b3-f6366bd7-d2d1-4a59-b26e-3f99ad406117-000000%40eu-central-1.amazonses.com.

Reply via email to