Well, you're right that going with a standard model with two ForeignKeys will lose some of the nice functionality associated with Django's ManyToMany field. That's just a fact of life at this point, I'm afraid. :( And no, Django doesn't create a separate class for the m2m table, it just keeps track of the SQL needed to deal with it.
I'm working on a patch to handle these situations, but I don't know how long it'll take to get ready and make it into trunk. For now, I'd recommend you go with the technique listed in the docs, and just use it without the nicer functionality that goes along with stadnard ManyToMany relationships. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
