2 Oct 2010 04:52
Re: Django expertise?
Thanks for the input, guys. I'll give it a go. On Fri, Oct 1, 2010 at 19:08, Rev. Johnny Healey <rev.null@...> wrote: > Use the existing django User model. So many things expect it that you'll > regret using anything else. > > sent from my shoe phone > > On Oct 1, 2010 7:02 PM, "Pete Hardie" <pete.hardie@...> wrote: >> On Fri, Oct 1, 2010 at 18:47, Richard Bronosky <Richard@...> >> wrote: >>> Don't ask to ask. Ask. >> >> "Do. Or do not. There is no try" :) >> >>> >>> On 10/1/10, John Anderson <sontek@...> wrote: >>>> Ask the questions >>>> >>>> >>>> >> >> Ok, I'm trying to build up a website, and was going to create a suer >> table in teh DB when I found the Django >> User class. My big question is: are there any reasons not to use the >> User class for my user table? I've seen the >> tutorial that mentions setting up a relationship to the User table for >> storing the app-specific data, so I know that it's >> doable, but is it wise? Are there issues that might make me wish I >> had used my own table?(Continue reading)
RSS Feed