irregardless of the "business logic" there's a simple caveat with web2py grid (and reference fields in general). for a field to be ordered (or searched, as it poses the exact same deal) correctly, web2py would have to fetch for each row of the table (not the page, the entire table) the reference record and build the string representation for it. Of course, this would mean killing performances at any level and with any backend.
"represent" can also accept a function, that further reduces the possibilities. references are a "subset" of the issue, that can be circumvented with a proper join and leaving the "leftiest" table (along with the correct field_id) as the one you'd like to edit. that being said, the grid is not (and can't be) a silver-bullet for every "business logic", but it closes most of the "needs" with little modification to the one-liner solution.... -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
