#29215: Document potential change to behaviour of QuerySet methods when
upgrading
to Python 3.6
-------------------------------------+-------------------------------------
Reporter: Matt Fisher | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution: invalid
Keywords: documentation | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => invalid
Comment:
There's not much we can realistically do here.
I'd say it would be border-line for whether to include it in the 1.11
porting topic page, but since that's no longer maintained that question is
moot.
I feel the issue itself out of scope for Django: we're generating correct
SQL, which is meant to be declarative, i.e. independent of how the RDMS
implements the query.
This falls with any number of backend specific quirks that we just can't
get into. (It's interesting what the Postgres folks would say about it.)
--
Ticket URL: <https://code.djangoproject.com/ticket/29215#comment:3>
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/068.df323d0b8ca326b77aaa632377dbcf25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
