Re: string-based fields and null

2009-11-26 Thread Tom Evans
On Thu, Nov 26, 2009 at 2:25 PM, chefsmart <moran.cors...@gmail.com> 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 TextFie

Re: string-based fields and null

2009-11-26 Thread chefsmart
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,

Re: string-based fields and null

2009-11-25 Thread Tim Valenta
il or (void *)0), so experienced programmers may have an easy > time > with maintenance or a NULL flag design. > > So, it's not a hard and fast rule.  I still think that inconsistent > backend support is the > major factor. > > Bill > > > > On Tue, Nov 24, 2009

Re: string-based fields and null

2009-11-25 Thread Bill Freeman
or factor. Bill On Tue, Nov 24, 2009 at 1:08 AM, chefsmart <moran.cors...@gmail.com> wrote: > The Django docs suggest "Avoid using null on string-based fields such > as CharField and TextField unless you have an excellent reason." > > ImageField, EmailField, FileField

string-based fields and null

2009-11-23 Thread chefsmart
The Django docs suggest "Avoid using null on string-based fields such as CharField and TextField unless you have an excellent reason." ImageField, EmailField, FileField, FilePathField, IPAddressField, SlugField, URLField, XMLField are also a string-based fields at the db level, so