On 5 sep, 17:27, Shawn Milochik <sh...@milochik.com> wrote: > You could use a model with three fields: > A generic foreign key to the instance to be modified. > A char field containing the fieldname on that instance. > The new value. > > Of course you'd need another field to store the user (assuming the > person making the authorization will base their decision on who's > making the request). Also, it'll get a little more complicated if you > want to store values for different field types (boolean vs. string, > for example), and maybe a boolean or a datetime field to indicate when > the request was accepted/denied. Then you can store a field indicating > whether it was approved or declined... > > So, the basics are at the top. Then you'll have to implement as much > of the rest as you'll need.
Thanks for your answer. I will try your solution. Sounds good! -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
