Files
web2py/gluon
niphlod d1ec005924 caches recursive selects for references
Why didn't we think before ? References are lazy, but when asked 
for representation why should we fetch the same referenced record
over and over ?

NB: the code caches only represent() fetching records from tables, that
are the only idempotent represent() calls out there. We could cache
every representation only asking for every represent() call to be 
idempotent. As I feel there will be someone returning random values,
I left it out.

I'll make a PR soon for pyDAL to fix the same behaviour.
2015-03-11 00:48:51 +01:00
..
2015-03-10 13:42:58 -05:00
2015-02-24 23:34:27 +01:00
2015-03-09 12:56:29 -05:00
2014-01-27 22:56:58 +01:00
2014-01-27 22:56:58 +01:00
2015-01-17 00:07:10 -06:00
2015-03-03 11:05:13 -06:00
2014-01-29 23:01:52 +01:00
2015-03-06 21:16:55 -05:00
2014-01-29 23:01:52 +01:00
2015-01-17 00:07:10 -06:00
2014-08-08 00:07:34 -05:00
2012-10-19 12:33:53 -05:00
2015-01-17 00:07:10 -06:00
2014-03-11 22:18:33 +01:00
2014-03-12 22:03:42 +01:00
2015-02-15 23:13:57 +01:00
2015-02-18 10:29:20 -06:00
2014-12-16 12:00:23 +00:00
2014-12-23 17:49:03 +01:00
2015-01-17 00:07:10 -06:00
2014-12-15 22:24:04 +01:00
2015-02-15 23:35:15 -06:00
2014-08-14 16:27:46 -05:00
2015-01-17 00:07:10 -06:00
2015-03-01 11:04:37 -06:00
2015-01-17 00:07:10 -06:00
2015-03-02 23:00:45 +01:00
2015-02-18 10:29:20 -06:00