Adding something about this to release notes shouldn't hurt anybody.
I will aim for a more generic wording about changes in the ORM. For
example, there are likely cases where the generated join aliases of the
query aren't the same as they were in 1.5. This could affect .extra()
users for example. Then there are all those changes that affect ORM
internal APIs, and there have been a lot of those changes.
- Anssi
On 11/05/2013 12:55 PM, jonas gastal wrote:
I wouldn't ask for a bug that has long existed to be considered a
release blocker. However a behavior change with no documentation is
not a nice thing to do to your users, it seems to me Elyézer makes a
good suggestion, informing users of the known bug in the release notes
seems quite reasonable.
Gastal
On Tue, Nov 5, 2013 at 8:09 AM, Elyézer Rezende <[email protected]> wrote:
Maybe it could be add to a "Known Bugs" or something like that section in
the release notes?
On Tue, Nov 5, 2013 at 3:42 AM, Anssi Kääriäinen <[email protected]>
wrote:
On Monday, November 4, 2013 8:16:12 PM UTC+2, [email protected] wrote:
I was going to file a ticket in trac about this and found this
one(https://code.djangoproject.com/ticket/21192) which seems related. The
thing is that one was supposedly resolved 5 weeks ago, which would mean that
fix would be in 1.6rc1...
Should I reopen that ticket or file a new one?
The issue about multiple filters for same relation in single .exclude()
query is tracked in #14645.
Just for the record: I don't consider the change in the original report's
query a release blocker (or a bug at all). The query works differently in
1.6.x, but as it didn't work correctly in 1.5.x either there is nothing to
do.
- Anssi
--
You received this message because you are subscribed to the Google Groups
"Django developers" 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].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/a901cb40-b80d-487e-b751-147471c94900%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Elyézer Rezende
http://elyezer.com
--
You received this message because you are subscribed to a topic in the
Google Groups "Django developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/django-developers/wQYmvtrTqIs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAFsoaZs2VWEzGgQ2GhvZbnprWJQrYy6bwWK-fmESZHEzaTCCPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Django
developers" 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].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5278D051.1030806%40thl.fi.
For more options, visit https://groups.google.com/groups/opt_out.
