There has been some change between 1.1 and trunk regarding questions whether to enforce defaults at the form or the model level. Might be relevant, or provide a clue: http://stackoverflow.com/questions/1436327/does-model-charfieldblankfalse-work-with-save
On Mar 17, 12:11 pm, Karen Tracey <[email protected]> wrote: > Yeah but, if it worked previously under 1.1, it ought not be broken by > updating to 1.2. > > Sounds like under 1.1 required=False on the form field overrode blank=False > on the model field, whereas with the current trunk required=False on the > form field is being ignored in favor of blank=False on the model field. > > It's probably worth opening a ticket; I don't recall hearing this reported > before. > > Karen -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
