orderby in a list sounds good. i've to use exec right now for some dynamic changing sort order with multi column.
-vince On Jan 18, 9:59 pm, Robin B <[email protected]> wrote: > To do this: > > db().select(db.person.ALL,orderby=˜db.person.name|db. > person.id) > > It would be better to do this: > > db().select(db.person.ALL,orderby=[˜db.person.name,db. > person.id]) > > Of course this would still work: > > db().select(db.person.ALL,orderby=˜db.person.name) > > It would be converted to this internally: > > db().select(db.person.ALL,orderby=[˜db.person.name]) > > The benefits of orderby=[...] are that you can more easily add, remove > or toggle a sort order, not to mention parsing the orderby=[...] in a > driver becomes trivial. > > Downsides? > > Robin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
