#14944: Saving a model which refers to unexistent models does not spit any
errors
---------------------------------------------------+------------------------
Reporter: ferran | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by Honza_Kral):
* status: new => closed
* resolution: => invalid
Comment:
The ORM doesn't do any validation by default, you have to do that manually
if you need it, see the docs for model validation for more details.
Normally the DB will complain of violating a constraint, you must be using
some DB that doesn't do that or have the table definitions in different
state than reflected by your models.py.
btw. your unique_together won't work like this, it must be a tuple of
tuples to work.
--
Ticket URL: <http://code.djangoproject.com/ticket/14944#comment:2>
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
