#36683: Update with Distinct Produces Unintentional Results
-------------------------------------+-------------------------------------
     Reporter:  Matt Shirley         |                    Owner:  Matt
         Type:                       |  Shirley
  Cleanup/optimization               |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  orm,distinct,update  |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):

 * resolution:   => fixed
 * status:  assigned => closed

Comment:

 In [changeset:"4744e9939b65d168c531e5e23d1ac8a4445ac7f9" 4744e99]:
 {{{#!CommitTicketReference repository=""
 revision="4744e9939b65d168c531e5e23d1ac8a4445ac7f9"
 Fixed #36683 -- Added error message on QuerySet.update() following
 distinct(*fields).
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36683#comment:8>
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 visit 
https://groups.google.com/d/msgid/django-updates/0107019a1c2cd63f-0df732b5-cb23-4725-b127-0b0f980d3729-000000%40eu-central-1.amazonses.com.

Reply via email to