On 5/18/2009 8:51 PM, palewire wrote: > I've stumbled my way into methods for automatically denormalizing > ForeignKey data -- and now see that better approaches have been > packaged up the very cool django-denorm (http://code.google.com/p/ > django-denorm/) -- which is great. > > But I'm curious to ask smarter people than myself about best practices > for denormalizing M2M relationships. The problem I've bumped into in > my feeble efforts is the same hurdle described concisely here: > > http://groups.google.com/group/django-users/browse_thread/thread/99680b69d2d4799c/07093d3695163269 > > So, rather than wait for ticket 5390 (http://code.djangoproject.com/ > ticket/5390) or another expansion in that direction, I thought I'd ask > the list since there's probably great concept for getting this done > that I'm ignorant of. I tried a scrub of Google and the list archives > without much luck, but please forgive me if I'm overlooking something > obvious.
You can always explicitly define the m2m model, then you can override the save() on that model if you like, or use signals like any other model. -- George --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
