Re: limit choices to logged-in user

2008-08-20 Thread Erik Allik
I'm just wondering, but in general, isn't the use of threadlocals kind of hacky? Shouldn't there be a more approach to this? Erik On 20.08.2008, at 0:12, brentp wrote: > > On Aug 19, 9:14 am, patrickk <[EMAIL PROTECTED]> wrote: >> it´s basically for autopopulating a form. I´m not setting the

Re: limit choices to logged-in user

2008-08-19 Thread brentp
On Aug 19, 9:14 am, patrickk <[EMAIL PROTECTED]> wrote: > it´s basically for autopopulating a form. I´m not setting the user > here, I just want data which is assigned to that user only. I could > use the forms __init__ to achieve this, but it´s easier to use > limit_choices ... moreover, the

Re: limit choices to logged-in user

2008-08-19 Thread patrickk
it´s basically for autopopulating a form. I´m not setting the user here, I just want data which is assigned to that user only. I could use the forms __init__ to achieve this, but it´s easier to use limit_choices ... moreover, the functionality of the admin-interface would reflect the

RE: limit choices to logged-in user

2008-08-19 Thread Emily Rodgers
> -Original Message- > From: django-users@googlegroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of patrickk > Sent: 19 August 2008 14:12 > To: Django users > Subject: limit choices to logged-in user > > > is there a way to limit choices (using foreign key) to the > logged-in user?