On Sep 2, 2007, at 4:18 PM, Mike Orr wrote:
> > I agree that the autosaving is the most confusing part of > Session.mapper, and the interface should require it to be explicitly > enabled: > Session.mapper(A, B, autosave=True) > > Both assign_mapper and Session.mapper have the assumption that "of > course everybody wants autosave", but that's not true. Some want the > .query attribute, some want autosaving, and some want both. At least > the .query attribute you can ignore if you don't want it, but there's > no way to disable autosaving. > of course adding a flag is the easy way to say "ok everyone can have what they want", but as we have all learned over the years, adding options adds confusion too. if we added "autosave", id leave it off by default, documented only in the docstrings, and otherwise not really advertise it. its really just a remnant of version 0.1 before we had a Session object. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
