[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

/var/log/cubicweb/*.log {

     2

        weekly

     3

        missingok

     4

        rotate 10

     5

        compress

     6

        delaycompress

     7

        notifempty

     8

        create 640 root adm

     9

        sharedscripts

    10

        postrotate

    11

           if [ -x /usr/sbin/invoke-rc.d ]; then \

    12

              invoke-rc.d cubicweb reload > /dev/null 2>&1; \

    13

           else \

    14

              /etc/init.d/cubicweb reload > /dev/null 2>&1; \

    15

           fi; \

    16

        endscript

    17

}