On 8/5/06, medhat <[EMAIL PROTECTED]> wrote:
>
> So, is there a way to not have to repeat the fields (from the example)
> "username" and "password" in the customer model? I wanted to achive
> something similar to this, but I don't want to duplicate the fields
Not through the 'save' method.
> (l
So, is there a way to not have to repeat the fields (from the example)
"username" and "password" in the customer model? I wanted to achive
something similar to this, but I don't want to duplicate the fields
(look at my related question in
http://groups.google.com/group/django-users/browse_thread/
Thanks for the tip. I've added conditions to ensure this is intended
behavior, based on your suggestion of checking self.id.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this grou
On 8/4/06, Dave <[EMAIL PROTECTED]> wrote:
>
> > I think your best bet is to override the save() method of your model.
>
> This worked perfectly. It didn't even occur to me that I could do that.
> Thanks so much for the suggestion.
Just be careful, because the save() will be called if you update
> I think your best bet is to override the save() method of your model.
This worked perfectly. It didn't even occur to me that I could do that.
Thanks so much for the suggestion.
- Dave Worley
--~--~-~--~~~---~--~~
You received this message because you are subsc
On 8/3/06, Dave <[EMAIL PROTECTED]> wrote:
>
> I'm creating an application for a client in which the Admin has a
> "customer" model. The admin area was easy to set up, and everything's
> working just swell under Apache 2.
>
> The challenge I'm facing, however, is that when the Admin (admin here
>
I believe there are articles on blogs and wiki posts about extending
the user model.
The basic idea as of right now (as far as I know), before model
inheritance is committed, is to connect the two using a foreign key.
If you want to create a user and relate it to the customer object, best
spot m
7 matches
Mail list logo
