That seemed like the solution. But render() returns a generator, and the json converter doesn't work with it directly. So, I could run it thru a for loop to materialize the rows, but that feels again like I'm beginning to swim upstream. Plus, I'd have to do this individually for each rest URL to have any control.
It just feels like I must be missing something important. Would it be better to not convert each club id into a name, and instead provide a list of rest links (URLs) which would retrieve all of the club data for a given id, for every club referenced? Is that "purer" rest (or even HATEOAS <http://en.wikipedia.org/wiki/HATEOAS>)? If I'm using this to make a table, it has the advantage of allowing each club to be a link that shows you all of the club's data. But it seem harder on the javascript side to build or fill in the table. -- Joe On Monday, September 1, 2014 11:07:06 AM UTC-7, Leonel Câmara wrote: > > Seems like you need this: > > http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Rendering-rows-using-represent > > This way you can render the fields using their represents before returning > them to the user. > -- 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.
