From b7644319e85ce38c1a576802317a9058a6aed82d Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 7 Apr 2017 14:18:22 -0400 Subject: Use baked lazyloading by default The ``lazy="select"`` loader strategy now makes used of the :class:`.BakedQuery` query caching system in all cases. This removes most overhead of generating a :class:`.Query` object and running it into a :func:`.select` and then string SQL statement from the process of lazy-loading related collections and objects. The "baked" lazy loader has also been improved such that it can now cache in most cases where query load options are used. Change-Id: Ic96792fffaa045ae9aa0a4657d6d29235d3efb85 Fixes: #3954 --- test/aaa_profiling/test_memusage.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'test/aaa_profiling') diff --git a/test/aaa_profiling/test_memusage.py b/test/aaa_profiling/test_memusage.py index e038d5c38..4a378d77d 100644 --- a/test/aaa_profiling/test_memusage.py +++ b/test/aaa_profiling/test_memusage.py @@ -263,7 +263,8 @@ class MemUsageWBackendTest(EnsureZeroed): del sessmaker go() - @testing.emits_warning("Compiled statement cache for.*") + @testing.emits_warning("Compiled statement cache for mapper.*") + @testing.emits_warning("Compiled statement cache for lazy loader.*") @testing.crashes('sqlite', ':memory: connection not suitable here') def test_orm_many_engines(self): metadata = MetaData(self.engine) -- cgit v1.2.1