#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 |
-------------------------------------+-------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"8ef3235034a1a7616714a5d61486dc68536f74ee"]:
{{{
#!CommitTicketReference repository=""
revision="8ef3235034a1a7616714a5d61486dc68536f74ee"
Fixed #19720 -- Oracle ordering related delete regression
When a query had a complex where condition (a condition targeting more
than the base table) a subquery was used for deletion. However, the
query had default ordering from the model's meta and Oracle doesn't
work with ordered subqueries.
The regression was caused by fast-path deletion code introduced in
1cd6e04cd4f768bcd4385b75de433d497d938f82 for fixing #18676.
Thanks to Dylan Klomparens for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19720#comment:2>
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.
