#7435: get_{next,previous}_by_someDateField() on unsaved objects should throw
meaningfull error
-------------------------------------+--------------------------------------
Reporter: telenieko | Owner: telenieko
Status: assigned | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by telenieko):
The docs-refactor broke the patch, always up-to-date patch
[http://www.marcfargas.com/gitweb/?p=django.git;a=commitdiff;h=trac/7435
-get-nextprev-error;hp=master here in colours] and
[http://www.marcfargas.com/gitweb/?p=django.git;a=commitdiff_plain;h=trac/7435
-get-nextprev-error;hp=master raw]
--
Ticket URL: <http://code.djangoproject.com/ticket/7435#comment:3>
Django Code <http://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 post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
