Thu, 25 Mar 2010 15:08:27 +0100 [c-c] new server_maintenance hook, called on c-c shell / upgrade stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 25 Mar 2010 15:08:27 +0100] rev 5019
[c-c] new server_maintenance hook, called on c-c shell / upgrade
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
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip