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

.TH cubicweb\-ctl 1 "2010-01-14" cubicweb\-ctl

     2

.SH NAME

     3

.B cubicweb\-ctl

     4

\- cubicweb control utility

     5

     6

     7

.SH SYNOPSIS

     8

.B  cubicweb-ctl <command>

     9

[

    10

.I OPTIONS

    11

] [

    12

.I <command arguments>

    13

]

    14

    15

.SH DESCRIPTION

    16

.PP

    17

CubicWeb utility to create and control instances, and more generally do all

    18

cubicweb's related tasks you can have to do using the command line. Available

    19

commands will depends on which part of the framework are installed.

    20

.PP

    21

Type

    22

.B "cubicweb\-ctl <command> \fB\-\-help\fR"

    23

for more information about a specific command.

    24

    25

.SH COPYRIGHT 

    26

Copyright (c) 2003-2010 LOGILAB S.A. (Paris, FRANCE).

    27

http://www.logilab.fr/ -- mailto:contact@logilab.fr