#13611: get_next_by_FOO allows nulls
---------------------------------------------------+------------------------
Reporter: CarlFK | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
You say "we" discussed this on IRC, but you don't say who "we" are. I
don't find the behavior you describe to be obvious or non-surprising. It's
also something you can add to your own models if you happen to need or
want the behavior as you describe it.
Marking wontfix; please open a discussion on django-dev if you are
especially passionate about this.
--
Ticket URL: <http://code.djangoproject.com/ticket/13611#comment:1>
Django <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.
