#19963: Add support for date_hierarchy across relations
-------------------------------+------------------------------------
Reporter: jbg@… | Owner:
Type: New feature | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by jbg@…):
This is purely a "practicality" suggestion, but given that this used to
work, and it doesn't look like it will work in 1.6 final, it may be worth
mentioning in the 1.6 release notes? Despite the fact that it was an
unsupported configuration and was not mentioned in the docs (as far as I
can tell), it worked fine, and if I'd been using it for months (after
assuming it would work, trying it out, and finding that it did work) then
I imagine other people might have been too.
So even just mentioning in the release notes, perhaps alongside the other
date-related backwards incompatibilities, that it no longer works in 1.6
might save a bunch of people a headache!
--
Ticket URL: <https://code.djangoproject.com/ticket/19963#comment:10>
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.f1723262e9042ed5935348d031403e5b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
