Tue, 28 Jul 2015 11:21:36 +0200 [web] fix AbstractSessionManager.clean_sessions (closes #5757240)
David Douard <david.douard@logilab.fr> [Tue, 28 Jul 2015 11:21:36 +0200] rev 10557
[web] fix AbstractSessionManager.clean_sessions (closes #5757240) sessions were not closed if "last_usage_time = session.cnx.check()" actually raises an AtributeError.
Tue, 21 Jul 2015 14:29:42 +0200 [migration/3.21] ask fewer questions
Julien Cristau <julien.cristau@logilab.fr> [Tue, 21 Jul 2015 14:29:42 +0200] rev 10556
[migration/3.21] ask fewer questions Several questions per table is just unreasonable.
Tue, 28 Jul 2015 11:26:47 +0200 [server] typo fix
Julien Cristau <julien.cristau@logilab.fr> [Tue, 28 Jul 2015 11:26:47 +0200] rev 10555
[server] typo fix
Tue, 28 Jul 2015 11:15:36 +0200 [test] check that we reject an rqlexpression in computed relation perms
Julien Cristau <julien.cristau@logilab.fr> [Tue, 28 Jul 2015 11:15:36 +0200] rev 10554
[test] check that we reject an rqlexpression in computed relation perms
Tue, 28 Jul 2015 09:25:26 +0200 Fix (de)serialization of ComputedRelation read permissions
Julien Cristau <julien.cristau@logilab.fr> [Tue, 28 Jul 2015 09:25:26 +0200] rev 10553
Fix (de)serialization of ComputedRelation read permissions For normal relation types, permissions don't need to be stored since they're just default values for the relation definitions. However, computed relations are serialized (as CWComputedRType), while their relation definitions are added at schema finalization time, and are only in memory. So add the 'read_permission' relation to CWComputedRType, and the appropriate hooks to save and restore those permissions. To avoid having to touch yams, we drop the 'add' and 'delete' permissions from the default computed relation permissions; this should probably be backported there. The actual permissions (set on the relation definitions) are hardcoded in finalize_computed_relations anyway. In deserialize_schema, the CWComputedRType handling needs to be delayed a little bit, until after we've called deserialize_ertype_permissions. The rql2sql test is adjusted because CWComputedRType has a 'name' attribute and the 'read_permission' relation, which generates ambiguity vs CWEType. We add an explicit CubicWebRelationSchema.check_permission_definitions, since we need to check both that computed and non-computed rtypes are defined properly. Based on report and initial patch from Christophe de Vienne (thanks!). Closes #5706307
Fri, 17 Jul 2015 16:48:43 +0200 Copy read permissions on ComputedRelation rdefs
Christophe de Vienne <christophe@unlish.com> [Fri, 17 Jul 2015 16:48:43 +0200] rev 10552
Copy read permissions on ComputedRelation rdefs Closes #5694110
Wed, 22 Jul 2015 19:50:50 +0200 [datafeed] fix typo in DataFeedXMLParser.is_deleted (closes #5729755)
David Douard <david.douard@logilab.fr> [Wed, 22 Jul 2015 19:50:50 +0200] rev 10551
[datafeed] fix typo in DataFeedXMLParser.is_deleted (closes #5729755)
Mon, 27 Jul 2015 10:51:29 +0200 [server/sources] make sure entity._cw is a Connection before calling Storages
Julien Cristau <julien.cristau@logilab.fr> [Mon, 27 Jul 2015 10:51:29 +0200] rev 10550
[server/sources] make sure entity._cw is a Connection before calling Storages The storage callbacks don't get an explicit Connection objects, so they go through entity._cw to access the repo and schedule operations. Since that entity object comes out of the entity cache, its _cw may be a web request instead of a Connection. So fix it up around the storage callbacks. Closes #5753543
Mon, 06 Jul 2015 14:34:41 +0200 [hooks] base64-encode extid before inserting it into moved_entities
Julien Cristau <julien.cristau@logilab.fr> [Mon, 06 Jul 2015 14:34:41 +0200] rev 10549
[hooks] base64-encode extid before inserting it into moved_entities If we insert the wrong value we're never going to find these entities again... Closes #5741105.
Tue, 21 Jul 2015 18:17:31 +0200 [hook] remove assumption about entity cache vs cw_edited
Julien Cristau <julien.cristau@logilab.fr> [Tue, 21 Jul 2015 18:17:31 +0200] rev 10548
[hook] remove assumption about entity cache vs cw_edited We were assuming that if an entity is in the connection's cache, it has a cw_edited attribute. This doesn't seem to always be the case. At least in cubicweb 3.21, merging the web and repo-side caches makes this more likely, but Denis says he's also seen this on 3.20.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip