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

action box

     2

    Area visible in the upper left column. You have a list of available actions on the entity. The most frequently used entry is `modify`.

     3

     4

object

     5

    All element created in the application

     6

    Example: project, ticket, user, ...

     7

     8

relation editing module

     9

    HTML widget that let you define new relations amongst objects.

    10

    11

relation

    12

    It's a kind of 'smart' link between 2 objets of the application. It has a specific sense that determine dynamic behaviour and add a new logic of the content.

    13

    14