Jae Kwon wrote: > > Thanks for looking. > > What happens when viewonly=False? > > I tried appending/popping from the list of related secondary objects > but I didn't see any duplicate inserts/deletes.
if you create new entities on the "secondary" table, and also insert records in the relation() with the "secondary", it will persist them separately. I have found myself using this pattern, however, since relation + secondary can create more efficient joins than an eagerload on an association object (the latter is solvable but it is a bit complex). > > - Jae > > > > On Sep 2, 2009, at 8:16 AM, Michael Bayer wrote: > >> >> "secondary" requires a Table object as its argument. it is not >> recommended to create a relation that uses a mapped table as its >> "secondary" unless the relation specifies viewonly=True. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
