#19720: Invalid SQL statement generated when deleting rows in Meta ordered
tables
(found using Oracle)
-------------------------------------+-------------------------------------
Reporter: dylan.klomparens@… | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version:
(models, ORM) | 1.5-beta-1
Severity: Release blocker | Resolution: fixed
Keywords: ORM SQL ordering | Triage Stage: Accepted
Meta | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by Anssi Kääriäinen <akaariai@…>):
In [changeset:"5cc0f5f8c1f35218ee4bce2d8c943a86f1888b96"]:
{{{
#!CommitTicketReference repository=""
revision="5cc0f5f8c1f35218ee4bce2d8c943a86f1888b96"
Made Query.clear_ordering force_empty arg mandatory
Previously it was possible to call clear_ordering without the
force_empty argument. The result was that the query was still ordered
by model's meta ordering if that was defined. By making the arg
mandatory it will be easier to spot possible errors caused by assuming
clear_ordering will remove all ordering.
Thanks to Dylan Klomparens for the suggestion. Refs #19720.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19720#comment:4>
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.
For more options, visit https://groups.google.com/groups/opt_out.
