#3134: [patch] The archive_year date-based generic view should not override a
model's default ordering
------------------------------------+---------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  jacob
     Type:  defect                  |       Status:  new  
 Priority:  normal                  |    Milestone:       
Component:  Generic views           |      Version:  SVN  
 Severity:  minor                   |   Resolution:       
 Keywords:                          |  
------------------------------------+---------------------------------------
Comment (by [EMAIL PROTECTED]):

 I've marked #3264 as a duplicate of this, as I think we have the better
 solution here.
 
 To compare the two: the patch at #3264 changes the {{{archive_year}}} view
 to use the model's default ordering (thus changing the behaviour of the
 view); this patch offers an optional parameter to specify ordering,
 defaulting to the current behaviour if left blank. There are also changes
 to the docs attached here.
 
 This ticket is missing unit tests though; unless anyone else provides them
 first I will add them when I can.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3134#comment:>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to