[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

# -*- coding: utf-8 -*-

     2

###############################################################################

     3

#

     4

# Put here information about external resources / styles used by your cube,

     5

# or to overides existing UI properties.

     6

#

     7

# Existing properties are available through the `sheet` dictionary available

     8

# in the global namespace. You also have access to a `data` function which

     9

# will return proper url for resources in the 'data' directory.

    10

#

    11

# /!\ this file should not be imported /!\

    12

###############################################################################

    13

    14

# CSS stylesheets to include in HTML headers

    15

# uncomment the line below to use template specific stylesheet

    16

# STYLESHEETS = sheet['STYLESHEETS'] + [data('cubes.%(cubename)s.css')]