Thu, 25 Mar 2010 14:49:24 +0100 [appobject] add version number to deprecation warning stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 14:49:24 +0100] rev 5018
[appobject] add version number to deprecation warning
Thu, 25 Mar 2010 14:33:50 +0100 update rql dependency
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 14:33:50 +0100] rev 5017
update rql dependency
Thu, 25 Mar 2010 14:26:13 +0100 backport stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 14:26:13 +0100] rev 5016
backport stable
Thu, 25 Mar 2010 14:25:44 +0100 fix migration script stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 14:25:44 +0100] rev 5015
fix migration script
Thu, 25 Mar 2010 14:00:01 +0100 [cleanup] useless try except stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 14:00:01 +0100] rev 5014
[cleanup] useless try except
Thu, 25 Mar 2010 13:59:47 +0100 [source storage] refactor source sql generation and results handling to allow repository side callbacks stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:59:47 +0100] rev 5013
[source storage] refactor source sql generation and results handling to allow repository side callbacks for instance with the BytesFileSystemStorage, before this change: * fspath, _fsopen function were stored procedures executed on the database -> files had to be available both on the repository *and* the database host * we needed implementation for each handled database Now, those function are python callbacks executed when necessary on the repository side, on data comming from the database. The litle cons are: * you can't do anymore restriction on mapped attributes * you can't write queries which will return in the same rset column some mapped attributes (or not mapped the same way) / some not This seems much acceptable since: * it's much more easy to handle when you start having the db on another host than the repo * BFSS works seemlessly on any backend now * you don't bother that much about the cons (at least in the bfss case): you usually don't do any restriction on Bytes... Bonus points: BFSS is more efficient (no queries under the cover as it was done in the registered procedure) and we have a much nicer/efficient fspath implementation. IMO, that rocks :D
Thu, 25 Mar 2010 13:49:07 +0100 [bfss] fix name error stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:49:07 +0100] rev 5012
[bfss] fix name error
Thu, 25 Mar 2010 13:46:55 +0100 [source storage] on deletion, entity has no edited_attributes stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:46:55 +0100] rev 5011
[source storage] on deletion, entity has no edited_attributes
Thu, 25 Mar 2010 13:44:24 +0100 [cleanup] rename dbms_helper to dbhelper for consistency stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:44:24 +0100] rev 5010
[cleanup] rename dbms_helper to dbhelper for consistency
Thu, 25 Mar 2010 13:42:17 +0100 [entity] we also have to override dict.pop to properly maintain edited_attributes consistency stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:42:17 +0100] rev 5009
[entity] we also have to override dict.pop to properly maintain edited_attributes consistency
Thu, 25 Mar 2010 13:41:26 +0100 [bfss test] some minor refactoring. Test deletion + creation/update/deletion rollback stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:41:26 +0100] rev 5008
[bfss test] some minor refactoring. Test deletion + creation/update/deletion rollback
Thu, 25 Mar 2010 13:27:09 +0100 don't put hooks deleting orphan composites into the 'integrity' category, we usually want it when integrity is deactivated stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 13:27:09 +0100] rev 5007
don't put hooks deleting orphan composites into the 'integrity' category, we usually want it when integrity is deactivated
Wed, 24 Mar 2010 18:38:23 +0100 [facet] allow to specify a target type on relation facets for case such as Keyword/CodeKeyword where we only targets Keyword stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 18:38:23 +0100] rev 5006
[facet] allow to specify a target type on relation facets for case such as Keyword/CodeKeyword where we only targets Keyword
Wed, 24 Mar 2010 18:38:19 +0100 don't rewrite config's url during migration stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 18:38:19 +0100] rev 5005
don't rewrite config's url during migration
Wed, 24 Mar 2010 18:04:59 +0100 le patch rql26 a été importé
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 18:04:59 +0100] rev 5004
le patch rql26 a été importé
Wed, 24 Mar 2010 17:58:05 +0100 backport stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 17:58:05 +0100] rev 5003
backport stable
Wed, 24 Mar 2010 15:18:48 +0100 [D] book: update backup procedures in additional tips stable
Julien Jehannet <julien.jehannet@logilab.fr> [Wed, 24 Mar 2010 15:18:48 +0100] rev 5002
[D] book: update backup procedures in additional tips
Wed, 24 Mar 2010 15:42:23 +0100 [cleanup] remove accidentaly commited print stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:42:23 +0100] rev 5001
[cleanup] remove accidentaly commited print
Wed, 24 Mar 2010 15:40:57 +0100 [test] don't try to reset session manager during test, stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:40:57 +0100] rev 5000
[test] don't try to reset session manager during test, this leads to weird failures when running multiple tests
Wed, 24 Mar 2010 15:22:01 +0100 don't update dontcheck until everything went fine: stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:22:01 +0100] rev 4999
don't update dontcheck until everything went fine: see usage in after_update_entity, where if we got an Unauthorized at hook time, we will retry and commit time.
Wed, 24 Mar 2010 15:21:21 +0100 [test] having two eid relations is now forbiden by rql stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:21:21 +0100] rev 4998
[test] having two eid relations is now forbiden by rql
Wed, 24 Mar 2010 15:09:49 +0100 [web test] a basic test, to be completed stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:09:49 +0100] rev 4997
[web test] a basic test, to be completed
Wed, 24 Mar 2010 15:09:21 +0100 [test] don't clear rtags during tests, may cause breakage with manually import appobjects modules (see unittest_tracker for instance) stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:09:21 +0100] rev 4996
[test] don't clear rtags during tests, may cause breakage with manually import appobjects modules (see unittest_tracker for instance)
Wed, 24 Mar 2010 15:08:24 +0100 [web] move workflow related uicfg stuff to the workflow module stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 15:08:24 +0100] rev 4995
[web] move workflow related uicfg stuff to the workflow module
Wed, 24 Mar 2010 14:17:01 +0100 dont get eid from entity's dict stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 14:17:01 +0100] rev 4994
dont get eid from entity's dict
Wed, 24 Mar 2010 14:12:47 +0100 [notification] don't create 'changes' in transaction data until actually needed stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 14:12:47 +0100] rev 4993
[notification] don't create 'changes' in transaction data until actually needed
Wed, 24 Mar 2010 14:11:01 +0100 backport pending_operations on hi-jacked session, see comment stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 14:11:01 +0100] rev 4992
backport pending_operations on hi-jacked session, see comment
Wed, 24 Mar 2010 13:51:52 +0100 [entity] fix dumb name error on .set_relations(rel=None) stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 24 Mar 2010 13:51:52 +0100] rev 4991
[entity] fix dumb name error on .set_relations(rel=None)
(0) -3000 -1000 -300 -100 -50 -28 +28 +50 +100 +300 +1000 +3000 tip