#3458: Blankable, non-nullable CharFields have a strange default behavior
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Validators
Version: 0.95 | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Comment (by [EMAIL PROTECTED]):
I think brosner's bug is slightly different, and I believe it's being
addressed in newforms. My bug is a bit simpler...when blank=True and
null=False, [] and None are still accepted as valid values.
--
Ticket URL: <http://code.djangoproject.com/ticket/3458#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
