Re: BooleanField and NullBooleanField (#2855 again)

2007-09-16 Thread SmileyChris
Reading http://code.djangoproject.com/ticket/3997, I think this covers the BooleanField side of thinsg On Aug 1, 2:12 pm, SmileyChris <[EMAIL PROTECTED]> wrote: > /me pulls out his horse-beating stick... > > First off, the patch in the ticket [1] this thread mentions isn't the > correct solution.

Re: BooleanField and NullBooleanField (#2855 again)

2007-07-31 Thread SmileyChris
/me pulls out his horse-beating stick... First off, the patch in the ticket [1] this thread mentions isn't the correct solution. Better would be to change the .get_default() method of BooleanField. [1] http://code.djangoproject.com/ticket/2855 On Jun 25, 1:06 pm, Malcolm Tredinnick <[EMAIL PROTE

Re: BooleanField and NullBooleanField (#2855 again)

2007-06-26 Thread Tai Lee
I would have thought it's obvious. Any fields are are not null=True must have a default specified in the model or a value explicitly provided before calling save(). However, I just did a quick double- take and it looks like CharField actually has an implicit default of "" already. If CharField can

Re: BooleanField and NullBooleanField (#2855 again)

2007-06-25 Thread Mads Sulau Joergensen
On Jun 25, 3:06 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Consistency in API seems to imply that "null=True" should always works > and permits empty values to be stored. It also means fields without a > default need a value to be set. You make a very good point. However I still think th

Re: BooleanField and NullBooleanField (#2855 again)

2007-06-24 Thread Malcolm Tredinnick
On Sun, 2007-06-24 at 08:35 -0700, Mads Sulau Joergensen wrote: > Hi. > > Having looked at #2855 and wondered the resolution of that ticket, There's been no resolution on that ticket, from what I can see. Still open. > i > wanted to raise the discussion again. > > To me, and many others, it m

Re: BooleanField and NullBooleanField (#2855 again)

2007-06-24 Thread Carl Karsten
Mads Sulau Joergensen wrote: > Hi. > > Having looked at #2855 and wondered the resolution of that ticket, i > wanted to raise the discussion again. > > To me, and many others, it makes absolutly no sense, that a > BooleanField with no default value given, sould yield a SQL error > uppon saving i

BooleanField and NullBooleanField (#2855 again)

2007-06-24 Thread Mads Sulau Joergensen
Hi. Having looked at #2855 and wondered the resolution of that ticket, i wanted to raise the discussion again. To me, and many others, it makes absolutly no sense, that a BooleanField with no default value given, sould yield a SQL error uppon saving it. The ticket states that a BooleanField sho