Wed, 09 Apr 2014 17:14:25 +0200 [repo] fix extid2entity to ensure connection's has a cnxset
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 09 Apr 2014 17:14:25 +0200] rev 9749
[repo] fix extid2entity to ensure connection's has a cnxset else we'll call source.doexec, which attempt to access to cnxset.cu, and crash in some case (eg unittest_cwxmlparser in sobjects/test). Also, manually switch to 'write' mode to ensure cnxset is not released until commit/rollback when some entity is inserted.
Wed, 09 Apr 2014 17:28:58 +0200 [test] update sobjects/test/unittest_cwxmlparser to cw 3.19 api
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 09 Apr 2014 17:28:58 +0200] rev 9748
[test] update sobjects/test/unittest_cwxmlparser to cw 3.19 api
Wed, 09 Apr 2014 17:15:25 +0200 [repo] make it clear in internal_cnx that security is disabled
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 09 Apr 2014 17:15:25 +0200] rev 9747
[repo] make it clear in internal_cnx that security is disabled as explained in its docstring. It was previously relying on internal connection's fake user (InternalManager) for read security and on disabling security hooks for write security. Using the security_enabled context manager is more readable and more reliable: while the older implementation works thanks to the InternalManager associated to the session, custom hooks should rely on session.[read|write]_security being correctly set. This change also allows selecting Password attributes in internal connections without explicitly disabling read security.
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip