Simplify and fix _cw.drop_entity_cache * it's never called with an eid as argument, beside in a useless case in test (removed) * the only place where it's called from outside the tests is in full-text reindexation in server.checkintegrity: we could removed the request implementation and move it in unittest_rset, byt I decided to keep it for consistency with all other entity cache handling methods * get back a fix from Julien Cristau for the connection's implementation, quoting is commit message: When removing an entity from the transaction's cache, clear the entity's own cache May avoid issues where an entity object is still accessible somewhere else (e.g. an operation) after dropping it from the transaction's cache, with a stale attribute or relation cache.

     1

/**

     2

 * .. function:: cw.utils.deprecatedFunction(msg, function)

     3

 *

     4

 * jQUery flattens arrays returned by the mapping function: ::

     5

 *

     6

 *   >>> y = ['a:b:c', 'd:e']

     7

 *   >>> jQuery.map(y, function(y) { return y.split(':');})

     8

 *   ["a", "b", "c", "d", "e"]

     9

 *   // where one would expect:

    10

 *   [ ["a", "b", "c"], ["d", "e"] ]

    11

 */

    12

 // XXX why not the same argument order as $.map and forEach ?

    13

    14

function map(func, array) {

    15

    var result = [];

    16

    for (var i = 0, length = array.length; i < length; i++) {

    17

        result.push(func(array[i]));

    18

    }

    19

    return result;

    20

}

    21

    22

    23

// skm cube still uses this

    24

getNodeAttribute = cw.utils.deprecatedFunction(

    25

    '[3.9] getNodeAttribute(node, attr) is deprecated, use $(node).attr(attr)',

    26

    function(node, attribute) {

    27

        return $(node).attr(attribute);

    28

    }

    29

);