Tue, 06 Jul 2010 11:31:04 +0200 [selectors] relation_possible selector should check user may read target entity type when specified stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 06 Jul 2010 11:31:04 +0200] rev 5900
[selectors] relation_possible selector should check user may read target entity type when specified
Tue, 06 Jul 2010 09:42:16 +0200 imported patch selstrfix.diff stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 06 Jul 2010 09:42:16 +0200] rev 5899
imported patch selstrfix.diff
Tue, 06 Jul 2010 09:42:13 +0200 imported patch rql2sqlfix.diff stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 06 Jul 2010 09:42:13 +0200] rev 5898
imported patch rql2sqlfix.diff
Tue, 06 Jul 2010 09:41:19 +0200 [migration] fix rename_entity_type to an existant entity type: get back relation from the old entity type non existant on the target type
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 06 Jul 2010 09:41:19 +0200] rev 5897
[migration] fix rename_entity_type to an existant entity type: get back relation from the old entity type non existant on the target type
Tue, 06 Jul 2010 09:39:06 +0200 cleanups
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 06 Jul 2010 09:39:06 +0200] rev 5896
cleanups
Mon, 05 Jul 2010 19:06:17 +0200 [selectors] avoid spurious warning when using implements by design
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 05 Jul 2010 19:06:17 +0200] rev 5895
[selectors] avoid spurious warning when using implements by design
Mon, 05 Jul 2010 19:05:56 +0200 [session] don't log reraised error occured during precommit
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 05 Jul 2010 19:05:56 +0200] rev 5894
[session] don't log reraised error occured during precommit
Mon, 05 Jul 2010 19:08:30 +0200 [doc] proof-reading and improvements
Nicolas Chauvat <nicolas.chauvat@logilab.fr> [Mon, 05 Jul 2010 19:08:30 +0200] rev 5893
[doc] proof-reading and improvements
Mon, 05 Jul 2010 18:25:25 +0200 [selectors] fix warning stack level
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 05 Jul 2010 18:25:25 +0200] rev 5892
[selectors] fix warning stack level
Mon, 05 Jul 2010 18:25:19 +0200 [schema migration] import refactoring to fix #1109558 and enhances things on the way
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 05 Jul 2010 18:25:19 +0200] rev 5891
[schema migration] import refactoring to fix #1109558 and enhances things on the way the main pb demonstrated by #1109558 was due to the fact that in-memory schema was updated in commit_event of operations. This is undesired in most cases, since we want the modification to be taken into account in the interval between the modification detection and the commit_event. I've fixed this by merging in-memory schema / database alteration operations for most important changes, doing in-memory schema changes as they are detected and implementing a revertcommit_event method to revert them if necessary (with exception for removal of stuff from the schema, where this is simply done in a postcommit_event methods). Also, I've benefited from this to support reverting of database alteration for some operations (more to be done there), and to move so system source alteration code to the native source code for a nicer design. There may be some more stuff in syncschema.py that would benefit from similar changes, but most important things are done (at least to close #1109558, w/ unittest_syncschema and unittest_migration green).
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip