Ohhh, so I've just been using association_proxy improperly. Darn interesting features! You just want to implement them, even when they're not appropriate. ;)
Anyway, thanks for the namespacing idea. That's exactly the kind of functionality I wanted to achieve, and I never would have thought of doing it like that. On Mar 23, 5:47 pm, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Mar 23, 2012, at 8:33 PM, Robert Rollins wrote: > > > > > I access the list of contacts which have been synced to a certain > > account by using Account.synced_contacts. However, I now realize that > > I don't know how to actually read and write > > AccountSyncedContact.unsubscribed from the Account.synced_contacts > > list. I haven't found any documentation on it. > > this is a puzzling question - the point of synced_contacts is to exclude the > need to access the .contact attribute of each AccountSyncedContact object. > If you in fact wanted a collection of objects that had a ".contact" and > ".unsubscribed" attribute, you'd read directly from synced_contact_assocs. > Third option, you want a namespace like ".email, .first_name, .last_name, > .unsubscribed" on each item - very easy, add those accessors to your > AccountSyncedContact object, i.e.: > > @property > def first_name(self): > return self.contact.first_name > > @property > def last_name(self): > return self.contact.last_name > > ...etc > > those are kind of the only three options I can think of here -- 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.
