Looks like a m2m class can be identified by the ._meta.auto_created attribute, which also holds the class with the m2m field. So the router can check for attributes on that class.
On Wed, Jan 4, 2012 at 11:49 AM, Brian Craft <bc...@thecraftstudio.com> wrote: > I strongly suspect the problem I'm having has to do with database > routers. It looks like under the hood django creates a model to > represent the m2m relationship, and the router is blocking the syncdb > for the generated model. > > I was using a class attribute on my models to control the routing, but > I don't have control of that on the generated model. > > On Wed, Jan 4, 2012 at 10:57 AM, Brian Craft <bc...@thecraftstudio.com> wrote: >> I have two models. The second one has a ManyToMany to the first. Both >> are managed. If I drop both tables and run syncdb, only the two model >> tables are created. There's no join table. syncdb doesn't report any >> errors. >> >> "validate" shows 0 errors. Any ideas what the problem could be, or how >> to debug it? I'm using multiple databases, and setting the table names >> for the two models via the Meta class. -- 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.
