Re: django.contrib.auth and username's field size

2013-08-02 Thread Tom Evans
On Fri, Aug 2, 2013 at 3:21 PM, Ivan Voras wrote: > 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/#speci

Re: django.contrib.auth and username's field size

2013-08-02 Thread Ivan Voras
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 > Hello, I have looked at th

Re: django.contrib.auth and username's field size

2013-07-27 Thread Russell Keith-Magee
On Sat, Jul 27, 2013 at 5:56 PM, Ivan Voras wrote: > Thanks, everyone! > > While I'm here: is there a way to create additional db objects in the > syncdb phase? Specifically, I'd like to create some database VIEWs as > a means of avoding using raw queries in my code. Ideally, I would like > a way

Re: django.contrib.auth and username's field size

2013-07-27 Thread Ivan Voras
Thanks, everyone! While I'm here: is there a way to create additional db objects in the syncdb phase? Specifically, I'd like to create some database VIEWs as a means of avoding using raw queries in my code. Ideally, I would like a way of specifying my own SQL which creates a Model's database objec

Re: django.contrib.auth and username's field size

2013-07-25 Thread Mike Dewhirst
On 26/07/2013 8:12am, Jonathan Baker wrote: Ideally your Django project would contain many different applications, which in turn have their own models.py module. I've yet to work on a project large enough to warrant that i try this, so what I'm about to say is completely untested... but I would t

Re: django.contrib.auth and username's field size

2013-07-25 Thread Jonathan Baker
Ideally your Django project would contain many different applications, which in turn have their own models.py module. I've yet to work on a project large enough to warrant that i try this, so what I'm about to say is completely untested... but I would think that creating a 'models' directory inside

Re: django.contrib.auth and username's field size

2013-07-25 Thread Ivan Voras
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 rathe

Re: django.contrib.auth and username's field size

2013-07-25 Thread Jonathan Baker
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 wrote: > Hello, > > I'm new to Django, and still f

django.contrib.auth and username's field size

2013-07-25 Thread Ivan Voras
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