Re: string-based fields and null

On Thu, Nov 26, 2009 at 2:25 PM, chefsmart wrote: > Those are good points. I am inclined to think the Django developers > think along the same lines (that is why they suggest to "Avoid using > null on string-based fields such as CharField and TextField unless you > have an excellent reason") > >

Re: string-based fields and null

Those are good points. I am inclined to think the Django developers think along the same lines (that is why they suggest to "Avoid using null on string-based fields such as CharField and TextField unless you have an excellent reason") Thus I am also inclined to think that CharField, ImageField etc

Re: string-based fields and null

In most cases, any string field should be allowed to be blank, and can easily survive WITHOUT "null=True". As stated before me, this is preferable. For instance, you asked about FileField, among others. This is perfectly fine to only use "blank=True". You'll primarily only be using "null=True" o

Re: string-based fields and null

The major problem that I see with NULL in strings is that there may be databases out there that don't distinguish between NULL and "", that is that store them the same way. "" is just as good in most cases. It behaves like False in python and template tag tests. And it has the advantage that if