niphlod / web2py

34%

master: 36%

LAST BUILD ON BRANCH enhancement/repr_cache

branch: enhancement/repr_cache

CHANGE BRANCH

x

Reset

• enhancement/repr_cache
• R-2.10.1
• R-2.10.2
• R-2.10.3
• R-2.10.4.beta
• R-2.9.10
• R-2.9.12
• contrib/appconfig
• docs/dal
• docs/n-p
• docs/new_structure
• enhancement/919
• enhancement/anyserver
• enhancement/js_norm_buttonname
• enhancement/makefile_coverage
• enhancement/scheduler
• enhancement/tests_with_travis_docker
• enhancement/travis
• enhancement/web2py_on_iis
• fix/1985
• fix/1998
• fix/2013
• fix/628
• fix/635
• fix/656
• fix/691
• fix/734
• fix/735
• fix/742
• fix/773
• fix/806
• fix/827
• fix/895
• fix/920
• fix/931
• fix/962
• fix/994
• fix/binaries_switch
• fix/bs3
• fix/bs3_grid_checkbox
• fix/cache_and_tests
• fix/cache_increment_and_tests
• fix/docs
• fix/duplicate_module
• fix/ilike
• fix/informix
• fix/issue679
• fix/json_and_decimals
• fix/mssql3_mappings
• fix/pg8000
• fix/pg8000_import
• fix/readme_badges
• fix/redis_cache_multiapp
• fix/redis_sessions
• fix/scheduler
• fix/sessions2trash
• fix/storage_and_tests
• fix/ubuntu_nginx_hardening
• fix/w2p_pack
• fix/windows_build
• issue/1980
• js/main_hook
• js/speed
• master
• scheduler/enhancement
• tests/html_and_serializers
• tests/languages_on_gae
• tests/validators
• travis/docker
• welcome/bootstrap_update

Build # 403

Build Type

push

travis-ci

Committed by niphlod

Commit Message

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.

Coverage Stats

8110 of 23887 relevant lines covered (33.95%)

0.34 hits per line