Fantastic, thanks for the info. On Thu, Sep 11, 2008 at 4:19 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 3:32 PM, Chris Stromberger < > [EMAIL PROTECTED]> wrote: > >> I'm wanting to use Django with a preexisting db. The db features a >> linking table (Many to Many). I'm wondering if I need to go ahead and >> define a model class for this table, or just add the ManyToMany field to one >> of the linked models. Or to put it another way, is there any way to define >> the relationship as a ManyToMany field w/o changing the table >> name/structure? Eg, in the online book example, the ManyToMany field >> generates a table with a specific name, specific fields and an >> auto-increment primary key. The existing many to many table I have does not >> match--name is different, obviously, and it only has the two foreign keys, >> both of which together form the primary key. >> Not sure how to handle this with models... >> > > Yes, define a model class for it, and then use the 'through' argument to a > ManyToMany field to define it as the model that acts as the intermediary for > the ManyToMany relation. See: > > > http://docs.djangoproject.com/en/dev/topics/db/models/#extra-fields-on-many-to-many-relationships > > This was added fairly recently so wouldn't be in the book. > > Karen > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
