Fri, 24 Jun 2011 16:59:45 +0200 [migration] litle enhancements and a fix to patch accidentally pushed two revisions ago stable
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
Thu, 23 Jun 2011 10:24:40 +0200 [controller] UndoController: fix output method (closes: #1776091) stable
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.
Fri, 24 Jun 2011 14:10:37 +0200 [migration] closes #1777411: schema modification commands shouldn't crash if already exists stable
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
Fri, 24 Jun 2011 14:02:29 +0200 [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 stable
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
(0) -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 tip