[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

Javascript Coding Standards

     2

---------------------------

     3

     4

(Draft, to be continued)

     5

     6

:Naming: camelCase, except for CONSTANTS

     7

     8

Indentation rules

     9

~~~~~~~~~~~~~~~~~

    10

- espace avant accolade ouvrante

    11

    12

- retour à la ligne après accolade ouvrante (éventuellement pas

    13

  de retour à la ligne s'il y a tout sur la même ligne, mais ce n'est

    14

  pas le cas ici.

    15

    16

- no tabs

    17

    18

    19

Documentation

    20

~~~~~~~~~~~~~

    21

XXX explain comment format for documentation generation

    22

    23

    24

Coding

    25

~~~~~~

    26

- Don't forget 'var' before variable definition, and semi-colon (';') after **each** statement.

    27

- Check the firebug console for deprecation warnings

    28

    29

    30

API usage

    31

~~~~~~~~~

    32

- unless intended, use jQuery('container') rather than jqNode('container')

    33

    34

    35

See also

    36

~~~~~~~~

    37

http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml