#32433: Delete distinct produces an unexpected and potentially harmful SQL
-------------------------------------+-------------------------------------
Reporter: egism | Owner: egism
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: orm, delete, | Triage Stage: Ready for
distinct | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"aa1aed923b391b56d514be499c4ddf4b5110b377" aa1aed92]:
{{{
#!CommitTicketReference repository=""
revision="aa1aed923b391b56d514be499c4ddf4b5110b377"
[3.2.x] Fixed #32433 -- Added error message on QuerySet.delete() following
distinct().
Backport of 6307c3f1a123f5975c73b231e8ac4f115fd72c0d from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32433#comment:9>
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/063.ca38a8de988d9e3c8038d0025645ed0d%40djangoproject.com.
