[rset] Always complete attribute/relation caches in ResultSet.get_entity RQL queries are often designed to fill up the ORM's caches when fetching entities out of the result set. Until now, if an entry already existed in the entity cache, ResultSet.get_entity would return it unchanged, not using the new ResultSet's contents to update the attribute cache, breaking expectations (if the attributes are needed, they'd then be fetched later one at a time, one entity at a time), resulting in loads of DB accesses. So we change ResultSet.get_entity so that: * if the entity is already cached and has been instantiated from the same rset, it is returned as-is (to avoid loops) * if the entity is not yet cached, it is instantiated * if the entity is cached via another rset, its attribute/relation caches are completed Closes #9942503

     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