Julien Cristau <julien.cristau@logilab.fr> [Thu, 05 Feb 2015 15:35:34 +0100] rev 10185
[pkg] 3.19.9
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 17:48:16 +0100] rev 10184
[hooks] don't insert use_email relation if the entity on either side is going away
Closes #4912946
Julien Cristau <julien.cristau@logilab.fr> [Fri, 16 Jan 2015 10:57:02 +0100] rev 10183
[undo] fix deletion of cw_source relation
Closes #4912882
Julien Cristau <julien.cristau@logilab.fr> [Thu, 15 Jan 2015 15:45:09 +0100] rev 10182
[hooks] don't insert an owned_by relation for deleted entities
If, in the same transaction, a composed entity is created and deleted,
we'll have scheduled a SyncOwnersOp which would end up creating an
owned_by relation for the deleted entity. Closes #4846883
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 29 Jan 2015 16:18:23 +0100] rev 10181
[etwist/service] adjust for a signature change
Closes #4878570.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 10 Dec 2014 10:49:07 +0100] rev 10180
[rset] fix crash on displaying rset where some symmetric relation is used. Closes #4739253
Avoid a KeyError.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 04 Dec 2014 11:37:10 +0100] rev 10179
Fix handling of limit within the primary view for related elements. Closes #4723579
* respect limit set by uicfg (like the 'autolimited' view itself does)
* set limit in rql query to one more than the specified one so the view knows
there are more things to display
Christophe de Vienne <christophe@unlish.com> [Mon, 29 Dec 2014 12:35:34 +0100] rev 10178
[native] Change SQL errors log level.
- The SQL error itself is logged as 'info'.
- The 'transaction has been rolled back' message is logged as 'debug'.
These log entries should not be critical:
- If an error occur at the sql level, it will be transmitted as a CW error.
The exception is raised and handled in a higher level function, which will
decide if it is critical or not.
- Admitting that rolling-back automatically on errors is wanted in some
cases, it cannot be considered 'critical'. The caller will receive the
original exception anyway, it is its job to decide if it is critical or
not.
Closes #4801120
Julien Cristau <julien.cristau@logilab.fr> [Mon, 02 Feb 2015 12:32:07 +0100] rev 10177
Added tag cubicweb-version-3.20.3, cubicweb-debian-version-3.20.3-1, cubicweb-centos-version-3.20.3-1 for changeset 7d3a583ed539
Julien Cristau <julien.cristau@logilab.fr> [Mon, 02 Feb 2015 12:17:29 +0100] rev 10176
[debian] build-depend on markdown for documentation build
Christophe de Vienne <christophe@unlish.com> [Wed, 28 Jan 2015 14:03:00 +0100] rev 10175
[devtools] Make PostgresTestDataBaseHandler multi-use friendly
Dont init the pgdb twice on the same datadir
- If two test case with the same apphome use a Postgres configuration, the
handler is initialised twice, so it has to check if the pgdb directory has
already been initialized.
- Work with the realpath of the pgdb
In some cases, the self.config.apphome will resolve symbolic links, but
not always.
It can result in an attempt to start twice the pg server for the same directory,
in the same test run... resulting in failure.
Closes #4875827
Julien Cristau <julien.cristau@logilab.fr> [Mon, 02 Feb 2015 12:07:10 +0100] rev 10174
[devtools] restore i18n of string removed in 4001cfe2f44d
Removing that string from the po files means that after running i18ncube
against newer cubicweb, we lose the translation when running on older
cubicweb's, which is probably not a good idea.