On Jun 1, 2007, at 5:58 PM, Mike Orr wrote:
> > Returning None is a Python standard, see list.sort(). Making select > generative is OK, but it should either modify the select in place or > return a new one, not modify it and return it. That's a Perlism. > "There should be one-- and preferably only one --obvious way to do > it." i am glad to see someone take a position on this. but the "modify in place and return it" thing is also how Hibernate criteria queries work. one advantage to modify in place (and not return it, or whatever) is one of performance....an app thats constantly generating a particular select in a generative fashion spends a lot of time creating and copying multiple select instances..and i think the overhead to creating a select() is higher than a mapper query since the select has more complicated state. thats the main reason im hesitant to make copying behavior in select() so prevalent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
