Mon, 21 Jun 2010 11:13:25 +0200 [repo] call entity.check() once before_update hooks has been called, to let them a chance to transform data stable cubicweb-version-3.8.5
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 11:13:25 +0200] rev 5808
[repo] call entity.check() once before_update hooks has been called, to let them a chance to transform data
Mon, 21 Jun 2010 10:42:26 +0200 3.8.5 stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 10:42:26 +0200] rev 5807
3.8.5
Mon, 21 Jun 2010 10:00:05 +0200 [debian] #1027463: logrotate script should filter out warnings stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 10:00:05 +0200] rev 5806
[debian] #1027463: logrotate script should filter out warnings
Mon, 21 Jun 2010 09:36:40 +0200 [schema migration] fix fix introduced in 5803:589e2e3fb997, test for backend alter column support should be done in the operation, else the associated index is not dropped while this is supported stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 09:36:40 +0200] rev 5805
[schema migration] fix fix introduced in 5803:589e2e3fb997, test for backend alter column support should be done in the operation, else the associated index is not dropped while this is supported
Mon, 21 Jun 2010 08:54:12 +0200 [schema migration] fix backend compatibility issue by using type_from_constraints / sql_change_col_type instead of bare ALTER COLUMN stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 08:54:12 +0200] rev 5804
[schema migration] fix backend compatibility issue by using type_from_constraints / sql_change_col_type instead of bare ALTER COLUMN
Mon, 21 Jun 2010 08:53:13 +0200 [schema migration] don't try to drop column if backend doesn't support column alteration (eg sqlite) stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 08:53:13 +0200] rev 5803
[schema migration] don't try to drop column if backend doesn't support column alteration (eg sqlite)
Mon, 21 Jun 2010 08:52:13 +0200 [session] when rollback_on_failure is false, we should not try to reconnect if the sql raised an error stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jun 2010 08:52:13 +0200] rev 5802
[session] when rollback_on_failure is false, we should not try to reconnect if the sql raised an error
Sun, 20 Jun 2010 15:09:42 +0000 Use SQL standard ALTER TABLE command (with ADD instead of ADD COLUMN) stable
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Sun, 20 Jun 2010 15:09:42 +0000] rev 5801
Use SQL standard ALTER TABLE command (with ADD instead of ADD COLUMN)
Sun, 20 Jun 2010 15:08:23 +0000 reduced logging verbosity in ldapuser source stable
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Sun, 20 Jun 2010 15:08:23 +0000] rev 5800
reduced logging verbosity in ldapuser source
Sat, 19 Jun 2010 16:08:54 +0200 use sessionid in log message stable
Alexandre Fayolle <alexandre.fayolle@logilab.fr> [Sat, 19 Jun 2010 16:08:54 +0200] rev 5799
use sessionid in log message
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip