[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 ...

     1

@echo off

     2

rem = """-*-Python-*- script

     3

rem -------------------- DOS section --------------------

     4

rem You could set PYTHONPATH or TK environment variables here

     5

python -x "%~f0" %*

     6

goto exit

     7

     8

"""

     9

# -------------------- Python section --------------------

    10

import sys

    11

from os.path import join, dirname, normpath

    12

sys.path.insert(0, normpath(join(dirname(__file__), '..', '..')))

    13

from cubicweb.cwctl import run

    14

run(sys.argv[1:])

    15

    16

DosExitLabel = """

    17

:exit

    18

rem """

    19

    20