[entity] ensure the .related(entities=False) parameter is honored all the way down (closes #2755994)
As of today, such a call will always fill the relation cache by
calling .entities() on every single related rset entry.
As a consequence, the `limit` parameter handling also had to be fixed.
It was bogus in the following ways:
* not used in the related_rql, hence potentially huge database
requests, but also actually
* foolishly used in the .entities()-calling cache routine we now
bypass (this changeset ticket's main topic)
Now:
* we set a limit on the rql expression, and
* forbid caching if given a non-None limit (as we don't want to make
the cache handling code more complicated than it is already)
With this, entity.unrelated gets a better limit implementation (so the
code in related/unrelated is nice and symmetric)
Risk:
* _cw_relation_cache disappears completely, which is good, but this is
Python, so you never know ...
from cubicweb.devtools.qunit import QUnitTestCase, unittest_main
from os import path as osp
class JScript(QUnitTestCase):
all_js_tests = (
("jstests/test_utils.js", (
"../../web/data/cubicweb.js",
"../../web/data/cubicweb.compat.js",
"../../web/data/cubicweb.python.js",
"jstests/utils.js",
),
),
("jstests/test_htmlhelpers.js", (
"../../web/data/cubicweb.js",
"../../web/data/cubicweb.compat.js",
"../../web/data/cubicweb.python.js",
"../../web/data/cubicweb.htmlhelpers.js",
),
),
("jstests/test_ajax.js", (
"../../web/data/cubicweb.python.js",
"../../web/data/cubicweb.js",
"../../web/data/cubicweb.compat.js",
"../../web/data/cubicweb.htmlhelpers.js",
"../../web/data/cubicweb.ajax.js",
), (
"jstests/ajax_url0.html",
"jstests/ajax_url1.html",
"jstests/ajax_url2.html",
"jstests/ajaxresult.json",
),
),
)
if __name__ == '__main__':
unittest_main()