[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

.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