Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 27 Jun 2011 15:30:52 +0200] rev 7562
backport stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 27 Jun 2011 15:17:52 +0200] rev 7561
Added tag cubicweb-debian-version-3.12.8-1 for changeset cf49ed55685a
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 27 Jun 2011 15:17:49 +0200] rev 7560
Added tag cubicweb-version-3.12.8 for changeset 50122a47ce4f
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 27 Jun 2011 13:59:07 +0200] rev 7559
3.12.8
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 24 Jun 2011 16:59:45 +0200] rev 7558
[migration] litle enhancements and a fix to patch accidentally pushed two revisions ago
Julien Jehannet <julien.jehannet@logilab.fr> [Thu, 23 Jun 2011 10:24:40 +0200] rev 7557
[controller] UndoController: fix output method (closes: #1776091)
Fix buggy direct output in `UndoController.publish()`.
Raise now a ValidationError instead of malformed string
Changes:
* raise ValidationError when an error occured in undo
* use the new message mechanism based on _cwmsgid
If errors are not fatal, you have to change publish() method.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 24 Jun 2011 14:10:37 +0200] rev 7556
[migration] closes #1777411: schema modification commands shouldn't crash if already exists
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 24 Jun 2011 14:02:29 +0200] rev 7555
[rqlrewrite] closes #1772135: 1. don't try to reuse a relation from another statement (eg because a subquery has been introduced) 2. _use_orig_term should consider the current statement
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 23 Jun 2011 07:41:25 +0200] rev 7554
test fixes
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 22 Jun 2011 18:53:38 +0200] rev 7553
[datafeed cw parser] refactor: split logic that was in the parser
into:
* an "item builder" component, turning an etree xml node into a specific
python dictionnary representing an entity
* "action" components, selected given an entity, a relation and its role
in the relation, and responsible to link the entity to given related
items (eg dictionnary)
This changes make it easy to add new action or to override existing
one's behaviour according to the entity, the relation, etc...
Also refactor the xml view so one can also override what's
included in the tag used to mark the entity as used by a relation,
hopefully allowing to reduce the number of http requests needed for
a full datafeed import.