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)
(0) -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 tip