On 11/3/06, yary <[EMAIL PROTECTED]> wrote: > > The idea here is that adding a 'realation_model' option to ManyToMany
This idea has been suggested previously, and has been rejected previously - it has some problems when you hit queries. > All queries seem pretty straightforward. In your example, yes. However, as always, the devil is in the detail. Consider: class ModelA(Model): name = CharField(...) class Relation(Model): name = CharField(...) class ModelB(Model): name = CharField(...) relation = ManyToManyField(ModelA, relation_model=Relation) What is the meaning of: ModelA.objects.filter(relation__name='foo') Does this query reference the name of the Relation model, or of ModelB? This is an artificial example, but it represents the crux of the problem - there is no easy way to integrate queries over the intermediate table without introducing ambiguities in queries over the related table. Come up with a clean syntax that differentiates the two, and we have a winner. So far, I haven't seen a viable option. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
