On further consideration of the interface, what about adding two new keywords to options() - mapper, and id? That way someone with a large group of options to set won't have to type the entity name and/or id on every single option.
session.query(Class).options(<options for main entity>).options(<options for other entity>, mapper=SomeClass, id="class1") On Dec 11, 8:26 pm, Chris M <[EMAIL PROTECTED]> wrote: > Don't care as long as the functionality is available somehow :) Unless > others have objections I say go with whatevers currently implemented. > > On Dec 11, 7:52 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > On Dec 11, 2007, at 6:21 PM, Chris M wrote: > > > > Okay, does this mean that options() doesn't go off the last entity or > > > is this interface just in addition to that behavior? > > > this currently is in lieu of the "options goes off the last entity" > > idea. i tried it that way but this way felt less surprising to me. > > we can do a poll if you want. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
