53da1e4794
Previously, you could explicitly assign None to a non-null ForeignKey (or other) field when creating the model (Child(parent=None), etc). We now throw an exception when you do that, which matches the behaviour when you assign None to the attribute after creation. Thanks to ales.zoulek@gmail.com and ondrej.kohout@gmail.com for some analysis of this problem. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9983 bcc190cf-cafb-0310-a4f2-bffc1f526a37 |
||
---|---|---|
.. | ||
fields | ||
sql | ||
__init__.py | ||
aggregates.py | ||
base.py | ||
expressions.py | ||
loading.py | ||
manager.py | ||
options.py | ||
query.py | ||
query_utils.py | ||
related.py | ||
signals.py |