Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Patrick J. Anderson
Malcolm Tredinnick wrote: > On Wed, 2006-10-11 at 22:45 -0500, Patrick J. Anderson wrote: > [...] >> Thanks for your comments, Malcolm. I realize that a determined person >> could submit an altered form and edit other profiles. >> >> I guess this is not a Django-specific question, but what would

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Patrick J. Anderson
Malcolm Tredinnick wrote: > On Wed, 2006-10-11 at 22:45 -0500, Patrick J. Anderson wrote: > [...] >> Thanks for your comments, Malcolm. I realize that a determined person >> could submit an altered form and edit other profiles. >> >> I guess this is not a Django-specific question, but what would

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Malcolm Tredinnick
On Wed, 2006-10-11 at 22:45 -0500, Patrick J. Anderson wrote: [...] > Thanks for your comments, Malcolm. I realize that a determined person > could submit an altered form and edit other profiles. > > I guess this is not a Django-specific question, but what would be the > best way of preventing

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Patrick J. Anderson
Malcolm Tredinnick wrote: > On Wed, 2006-10-11 at 21:33 -0500, Patrick J. Anderson wrote: > [...] >> I guess the concept of approving members needs to be refined. My project >> has some "special" requirements and this is one of them. > > There's no problem with special requirements. My point was

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Patrick J. Anderson
Malcolm Tredinnick wrote: > On Wed, 2006-10-11 at 21:33 -0500, Patrick J. Anderson wrote: > [...] >> I guess the concept of approving members needs to be refined. My project >> has some "special" requirements and this is one of them. > > There's no problem with special requirements. My point was

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Malcolm Tredinnick
On Wed, 2006-10-11 at 21:33 -0500, Patrick J. Anderson wrote: [...] > I guess the concept of approving members needs to be refined. My project > has some "special" requirements and this is one of them. There's no problem with special requirements. My point was that it's not at all secure to incl

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Patrick J. Anderson
Malcolm Tredinnick wrote: > On Wed, 2006-10-11 at 15:07 -0500, Patrick J. Anderson wrote: >> I have extended Django User model (site members as opposed to users) and >> I want to approve them before they can use all site features. Below is >> my model: >> >> class Member(models.Model): >> u

Re: NullBoolean/Boolean Field weirdness

2006-10-11 Thread Malcolm Tredinnick
On Wed, 2006-10-11 at 15:07 -0500, Patrick J. Anderson wrote: > I have extended Django User model (site members as opposed to users) and > I want to approve them before they can use all site features. Below is > my model: > > class Member(models.Model): > user = models.ForeignKey(User) >

NullBoolean/Boolean Field weirdness

2006-10-11 Thread Patrick J. Anderson
I have extended Django User model (site members as opposed to users) and I want to approve them before they can use all site features. Below is my model: class Member(models.Model): user = models.ForeignKey(User) ... is_approved - models.NullBooleanField(default = False)