On 1-12-2005, at 6:52, Kenneth Gonsalves wrote:
title = meta.CharField('Title',maxlength=250)
From http://www.djangoproject.com/documentation/model_api/#general-
field-options:
null
If True, Django will store empty values as NULL in the database.
Default is False.
Note that empty string values will always get stored as empty
strings, not as NULL -- so use null=True for non-string fields such
as integers, booleans and dates.
Avoid using null on string-based fields such as CharField and
TextField unless you have an excellent reason. If a string-based
field has null=True, that means it has two possible values for "no
data": NULL, and the empty string. In most cases, it's redundant to
have two possible values for "no data;" Django convention is to use
the empty string, not NULL.
blank
If True, the field is allowed to be blank.
Note that this is different than null. null is purely database-
related, whereas blank is validation-related. If a field has
blank=True, validation on Django's admin site will allow entry of an
empty value. If a field has blank=False, the field will be required.
p = visitors.Visitor(title=l'title')
p.save()
it saves, pg doesnt barf, and i get '' values in all the text
fields. I feel the behaviour should be a barf from pg.
Strange, IIRC this type of error is presumed to be catch by model
validators before data gets sent to database, or I'm guessing it
wrong? It is not question why database is not sending a error, but
why django model validators allow sending this to database.
btw.
approved = meta.BooleanField('Approved',default='true')
it should be:
approved = meta.BooleanField(default=True)
always use python native types when working with models - it will be
converted to database specific automatically. Also, if you don't use
any of i18n stuff you don't need to specify verbose_name if is same
as a field name.
---
Nebojša Đorđević - nesh
Studio Quattro - Niš - SCG
http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/
Registered Linux User 282159 [http://counter.li.org]
