#9039: Form validation problem for model with ForeignKey having
unique=True,blank=True,null=True
-----------------------------------+----------------------------------------
Reporter: nategriswold | Owner: kmtracey
Status: reopened | Milestone:
Component: Forms | Version: 1.0
Resolution: | Keywords: model-validation
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Comment (by kmtracey):
Ugh. Agreed that best would be if we could validate the form in a way
that matched what the backend was going to enforce, but we don't seem to
have anything like that in place and like you I'd be wary of moving in
that direction. Could we just remove the 2nd save in the testcase to
avoid triggering the error? We're left with a form that will validate
when the acutaul DB save() is going to fail on at least one backend. Not
ideal but more attractive to me than having the form refuse to validate
values that some DBs find acceptable. And in the general case form
validation doesn't guarantee that the DB save is actually going to work,
so code should be prepared to deal with DB errors even after a successful
validate()...right?
--
Ticket URL: <http://code.djangoproject.com/ticket/9039#comment:11>
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-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
-~----------~----~----~----~------~----~------~--~---
