Thanks! While I have a newbie thread going, let me ask you one more thing: I like the concepts behind Django models, but what are the best practices for organizing models into files for large-ish scale projects? Keeping all model classes in a single models.py file is not scalable, and I'd rather have a file-per-class situation, at least for some of them. The reason for this is that I suspect the models will grow functionalities encapsulating more complex behaviour than simple database operations.
Or is the best practice to keep models simple - basically a database schema description - and create new, more complex classes containing specific code? On Thursday, 25 July 2013 23:36:49 UTC+2, jondbaker wrote: > > Hi Ivan, and welcome. Django >= 1.5 features custom User models, which I > believe would solve your problem: > https://docs.djangoproject.com/en/dev/topics/auth/customizing/#specifying-a-custom-user-model > > > On Thu, Jul 25, 2013 at 3:25 PM, Ivan Voras <ivo...@gmail.com<javascript:> > > wrote: > >> Hello, >> >> I'm new to Django, and still finding out how it all fits together. I've >> seen django.contrib.auth and I'm wondering - is it a common practice to >> actually use it as a basis for application authentication? >> >> If so, I have a question: the username field as defined (30 characters) >> is too short for me. Is there an easy way to override the default field >> size? >> >> What I'm actually trying to do is this: I'm thinking of using e-mail >> addresses for user names, with the "username" field holding a lowercase >> address (to make use of the unique index) and the "email" field will store >> the address as entered by the user. The default length of the "email" field >> is good enough (75) but the "username" field is too short. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/django-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Jonathan D. Baker > Developer > http://jonathandbaker.com > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
