Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 19 May 2011 16:39:24 +0200] rev 7402
[facets/table] vertically group facets by two when possible in order to have a more compact horizontal layout in table filter form
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 15:56:49 +0200] rev 7401
[workflow] add method on IWorkflowable to set initial state of an entity (closes #1686357)
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 11:50:54 +0200] rev 7400
[web test] fix test broken by making cw_source editable by managers
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 10:53:17 +0200] rev 7399
[multi-sources] support for moving an entity from an external source (closes #343818)
Original need is to move a user from a ldap source to the system source so
we can delete it from ldap without loosing information into the cubicweb
instance.
We can't wait for the user to be deleted from the ldap since it will be too
late then to get back user attributes, so it has to be a manual operation to
operate before actual deletion. This makes sense for other sources as well.
So the idea is to make the "Any cw_source CWSource" relation editable by
managers, and to watch changes of it. We then check the move is possible
(ie from an external source to the system source) and do necessary stuff
(essentially changing source information and copying data into the system
source).
Remaining pb is that we don't want the moved entity to be reimported later.
To distinguish this state, the trick is to change the associated record in
the 'entities' system table with eid=-eid while leaving other fields
unchanged, and to add a new record with eid=eid, source='system'. External
source will then have consider case where `extid2eid` return a negative eid
as 'this entity was known but has been moved, ignore it'.
Notice no ui is provided yet, it has currently to be done in a c-c shell.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 10:53:11 +0200] rev 7398
[repository api] definitly kill usage of word 'pool' to refer to connections set used by a session
Also document session's data storage and some other internals.
Hopefuly things will get clearer.
Closes #1684860: vocabulary confusion in repository code: notion of 'pool'
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 10:36:26 +0200] rev 7397
backport stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 10:35:20 +0200] rev 7396
[rql2sql] fix in 7394:d11d88bd08e8 was actually not needed
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 09:43:23 +0200] rev 7395
[rset] close #1683703: rset.get_entity crash on rql query with subquery and aggregat
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 19 May 2011 09:40:44 +0200] rev 7394
[rql2sql] fix generated sql for eid comparison. closes #1638695
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 18 May 2011 16:05:11 +0200] rev 7393
fix some deprecation warnings