Well, that's basically what my suggested quickSelect() method is doing... But as you said - out of the box, there is a 'colname' argument that is disregarded inside the 'as_dict' if-block, so you can only get a practically-unusably-orgeenized pile of values in each record in the record-set... Having the table+column names ordered as they were in the query-string itself, as the mapping-source for the disctionary-keys of each record, is what I am really proposing here - and it is SOOO simple and short to implement...
As for being it an attribute of the .select() method, or a separate method, is generally a matter of personal-taste, I thing - I initially had like a 'quick' default-argument added to the original .select() method, and had that "popped"-out of the **arguments dictionary with a Fals'y default... That's a minor api-structure detail, I personally don't care that much... I DO, however, recoil form the idea of having all of my selects in my application look like: "db.executesql(db(query)._select(<my-selection-attrs>), as_dict=True, colname=<some-list-of-column-and-field-names-from-somewhere>) ... That's just way too ugly for my taste... -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
