Wed, 26 Mar 2014 11:08:09 +0100 [migration] Improve update of in-memory schema during 3.18 CWAttribute.defaultval change stable
Julien Cristau <julien.cristau@logilab.fr> [Wed, 26 Mar 2014 11:08:09 +0100] rev 9589
[migration] Improve update of in-memory schema during 3.18 CWAttribute.defaultval change We weren't updating the schema properly so a bunch of structures still had the old rdef with 'String' as object. That caused failures to add new attributes later in the migration as their default value would be a Binary object but the schema would expect a String. Closes #3683640
Thu, 27 Mar 2014 14:32:21 +0100 [migration] always rebuild infered relation stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 27 Mar 2014 14:32:21 +0100] rev 9588
[migration] always rebuild infered relation This was skipped for some bad reason (see 12ad88615a12 which introduced the change). Fix for #231956 in Yams is necessary to allow this cset: during a migration, we want to always reinfer relations while allowing explicit redefinition of an infered relation later. Else, we may run the migration with missing parts of the schema (the one that should have been infered). Closes #3685463.
Mon, 24 Mar 2014 16:29:18 +0100 Backout "[web/navigation] use add_onload instead of inline javascript href" stable
Julien Cristau <julien.cristau@logilab.fr> [Mon, 24 Mar 2014 16:29:18 +0100] rev 9587
Backout "[web/navigation] use add_onload instead of inline javascript href" This reverts changeset 170e1437948d, for at least two reasons: the PageNavigationSelect component was not updated for the new type of navigation links, and external cubes defining View.page_navigation_url exist in the wild and also got broken navigation links. This reopens #3501626 and closes #3677945.
Fri, 14 Mar 2014 10:51:05 +0100 [test] those are rql tests, not cubicweb (and they break with rql 0.31.5). Remove them. stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 14 Mar 2014 10:51:05 +0100] rev 9586
[test] those are rql tests, not cubicweb (and they break with rql 0.31.5). Remove them.
Mon, 24 Mar 2014 18:14:22 +0100 [source/native] allow many eid creation per .create_eid call (closes #3526594)
Aurelien Campeas <aurelien.campeas@logilab.fr> [Mon, 24 Mar 2014 18:14:22 +0100] rev 9585
[source/native] allow many eid creation per .create_eid call (closes #3526594) [jcr: move migration code to bootstrapmigration_repository.py to make sure we stop using the old sequence ASAP]
Thu, 06 Feb 2014 19:04:03 +0100 [pkg] bump the dependency on logilab.database
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 06 Feb 2014 19:04:03 +0100] rev 9584
[pkg] bump the dependency on logilab.database This will allow use of an extended API. Related to #3526594.
Mon, 10 Mar 2014 15:55:56 +0100 [source/native] refactor eid generation code
Aurelien Campeas <aurelien.campeas@logilab.fr> [Mon, 10 Mar 2014 15:55:56 +0100] rev 9583
[source/native] refactor eid generation code This set of related methods clutters the native source API. It will be better served with a dedicated eid genrator object. Related to #3526594. [jcr: allocate the eid generator in __init__]
Mon, 24 Mar 2014 11:57:23 +0100 Move entity cache from web.request.ConnectionCubicWebRequestBase to repoapi.ClientConnection
Julien Cristau <julien.cristau@logilab.fr> [Mon, 24 Mar 2014 11:57:23 +0100] rev 9582
Move entity cache from web.request.ConnectionCubicWebRequestBase to repoapi.ClientConnection ResultSet._build_entity relies on an entity cache to avoid going round in circles (stack overflow due to infinite recursion) e.g. in a postcreate script. Clear the cache at commit/rollback time to avoid unexpected side effects; and explicitly clear the cache in a few tests where we mix ORM and RQL using the same connection.
(0) -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 tip