#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         
------------------------------+---------------------------------------------
Changes (by [EMAIL PROTECTED]):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 Is this bug saying that if a database field is set with blank=True and
 default=whatever and the value is not present with a form submission then
 it should fallback to the value of default?  I am running into this
 problem with a few of my forms and I have to manually add in a default
 value right before the object gets saved.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3458#comment:2>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to