Tue, 04 Feb 2014 15:06:25 +0100 Add a db-statement-timeout option for postgresql sources
Julien Cristau <julien.cristau@logilab.fr> [Tue, 04 Feb 2014 15:06:25 +0100] rev 9724
Add a db-statement-timeout option for postgresql sources Use that new option to set the statement_timeout option when creating connections, except for maintenance operations (shell and upgrade). Closes #2547026
Fri, 18 Apr 2014 14:24:52 +0200 [test] use assertNotIsInstance instead of assert_(not isinstance(...))
Julien Cristau <julien.cristau@logilab.fr> [Fri, 18 Apr 2014 14:24:52 +0200] rev 9723
[test] use assertNotIsInstance instead of assert_(not isinstance(...))
Wed, 23 Apr 2014 18:19:37 +0200 [services] register_user now returns the new CWUser
Julien Cristau <julien.cristau@logilab.fr> [Wed, 23 Apr 2014 18:19:37 +0200] rev 9722
[services] register_user now returns the new CWUser Closes #3804444
Wed, 23 Apr 2014 18:41:34 +0200 [server/session] remove json dumps around call_service
Julien Cristau <julien.cristau@logilab.fr> [Wed, 23 Apr 2014 18:41:34 +0200] rev 9721
[server/session] remove json dumps around call_service This backouts changeset b151beea9cb6. With call_service being in-process and synchronous, there's no RPC use case.
Wed, 30 Apr 2014 08:07:59 +0200 [req.find] Use vreg.schema.eschema for eschema lookup
Christophe de Vienne <cdevienne@gmail.com> [Wed, 30 Apr 2014 08:07:59 +0200] rev 9720
[req.find] Use vreg.schema.eschema for eschema lookup If an etype is non-existant, using vreg.schema[etype] raises a confusing error complaining about a non-existing relation. This is because of the implementation of vreg.schema.__getitem__ that look first in entities and then in relations. Using directly vreg.schema.eschema restrict the lookup to etypes only, hence raises a meaningful error when the etype does not exist.
Wed, 30 Apr 2014 10:13:10 +0200 [doc] Typo
Christophe de Vienne <cdevienne@gmail.com> [Wed, 30 Apr 2014 10:13:10 +0200] rev 9719
[doc] Typo
(0) -3000 -1000 -300 -100 -30 -10 -6 +6 +10 +30 +100 +300 +1000 +3000 tip