ah yes, threadlocals... i was thinking maybe there was a newer way. its nice how you can override the queryset method of a ModelAdmin class because that gets passed a request. I was hoping there'd be some similar new functionality with the ModelForm class...
thx keith On Tue, Oct 14, 2008 at 4:10 PM, gearheart <[EMAIL PROTECTED]> wrote: > > http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser > > lingrlongr wrote: > > What's the best way to always set a User foreign key to the current > > user using the admin site? For example: > > > > # models.py > > class MyModel(models.Model): > > my_data = models.CharField(max_length=50) > > user = models.ForeignKey(User) > > > > When this was saved/updated in the admin, "user" should always equal > > the person saving/updating the object. I'd also like for the user > > field to not even show up... > > > > thx. > > > > keith > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
