Thu, 04 Dec 2014 11:37:10 +0100 Fix handling of limit within the primary view for related elements. Closes #4723579
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
Mon, 29 Dec 2014 12:35:34 +0100 [native] Change SQL errors log level.
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
Mon, 02 Feb 2015 12:32:07 +0100 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: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
(0) -10000 -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 tip