Re: Model Basics

On 2/28/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > Yeah, we talked about this on Sunday at the Django sprint. The > tentative plan is to introduce a CurrentUserField which is > special-cased in the admin logic. How would this be handled in user code? How would Manipulators deal with

Re: Model Basics

On 2/28/06, DaveW <[EMAIL PROTECTED]> wrote: > I see that ticket #1268 has been closed as WontFix - threadlocal is > felt to be to heavyweight a solution. Unfortunately, some mechanism for > this is going to be needed for Django to be used in many corporate > environments - has anyone had any

Re: Model Basics

I see that ticket #1268 has been closed as WontFix - threadlocal is felt to be to heavyweight a solution. Unfortunately, some mechanism for this is going to be needed for Django to be used in many corporate environments - has anyone had any other thoughts about how to implement this?

Re: Model Basics

Thanks, I wasnt sure from the documentation if subclassing would do a "inheritance" DB thing like many ORM tools support, or simply combine the two classes as I was hoping for.

Re: Model Basics

2006/2/12, ChaosKCW <[EMAIL PROTECTED]>: > 1) can you access the session user object from the model _pre_save no see http://code.djangoproject.com/ticket/1268 though > 2) can you subclass a model. yes see the docs (either on www.djangoproject.com/documentation or the wiki on

Re: Model Basics

PS the project and app level DB would also allow for creater scalablity and better seperation of concerns. One last question, is it possible to add a glboal hook into the ORM layer ala SOX requiremens i the USA. To proide an audit of any transaction ?