#29847: Window function test failures with MySQL 8
-------------------------------------+-------------------------------------
Reporter: Tom Forbes | Owner: Tom
| Forbes
Type: Bug | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Florian Apolloner <apollo13@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"c53af5661313079d022553b6c775e6c4f8d34927" c53af56]:
{{{
#!CommitTicketReference repository=""
revision="c53af5661313079d022553b6c775e6c4f8d34927"
Fixed #29847 -- Ensured proper ordering in queries.
Even though good databases tend to keep the result sorted by the/one
window expression and the planners are smart enough to not resort if not
required, it is not valid to rely on this.
MariaDB specifically did return whatever order it wanted, which is
completely okay. Now we sort towards the expected data for all databases.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29847#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.9d18b32cc9ed2974a62dce8dcf8a301d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
