Re: default/null fields in models

2006-03-01 Thread xamdam
excellent, thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EM

Re: default/null fields in models

2006-03-01 Thread Malcolm Tredinnick
On Wed, 2006-03-01 at 22:21 +, xamdam wrote: > I have a model with a CharField(null=True, default='') > > In admin interface the field still appears 'required', whether or not I > make it visible in field_list That is correct (and not a bug). If you want to allow empty values (i.e. the field

Re: default/null fields in models

2006-03-01 Thread James Bennett
On 3/1/06, xamdam <[EMAIL PROTECTED]> wrote: > Using no-magic branch from about a couple of weeks ago. If possible, update your copy of magic-removal to the latest revision; there's been a HUGE amount of work done on it recently, and if this is a bug it may already have been fixed. If you still s

default/null fields in models

2006-03-01 Thread xamdam
I have a model with a CharField(null=True, default='') In admin interface the field still appears 'required', whether or not I make it visible in field_list I also have a BooleanField(null=True), about which admin does not complain interestingly, from manage.py shell, there are no complaints, e