Thu, 18 Feb 2010 14:06:17 +0100 missed conflict stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 14:06:17 +0100] rev 4637
missed conflict
Thu, 18 Feb 2010 14:02:48 +0100 backport lost stable head stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 14:02:48 +0100] rev 4636
backport lost stable head
Thu, 18 Feb 2010 13:31:03 +0100 fix sync_schema_props_perms test stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 13:31:03 +0100] rev 4635
fix sync_schema_props_perms test
Thu, 18 Feb 2010 13:30:37 +0100 fix create_user function introduced in d6ae30c5d055 for database initialization: messup admin user groups when anon is created due to missing restriction stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 13:30:37 +0100] rev 4634
fix create_user function introduced in d6ae30c5d055 for database initialization: messup admin user groups when anon is created due to missing restriction
Thu, 18 Feb 2010 13:28:38 +0100 3.6 api update stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 13:28:38 +0100] rev 4633
3.6 api update
Thu, 18 Feb 2010 12:58:52 +0100 fix unittest_hooks: attributes have now update_permission instead of [add/delete]_permission stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 12:58:52 +0100] rev 4632
fix unittest_hooks: attributes have now update_permission instead of [add/delete]_permission
Thu, 18 Feb 2010 12:57:57 +0100 when modifying a persistent schema, erschema may miss some permissions which wil trigger a key error, but we don't want to crash on such cases stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 12:57:57 +0100] rev 4631
when modifying a persistent schema, erschema may miss some permissions which wil trigger a key error, but we don't want to crash on such cases
Thu, 18 Feb 2010 12:52:34 +0100 fix #694445: related entity generates weird RQL which in turn generates weird SQL which fails on SQL Server stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 12:52:34 +0100] rev 4630
fix #694445: related entity generates weird RQL which in turn generates weird SQL which fails on SQL Server quick fix to reuse modification_date if already retreived by the rql query.
Thu, 18 Feb 2010 12:13:36 +0100 fix 4626:c26b4df9fc90 (#703911): use can't rely on peid since it's not an actual eid when we're creating the parent entity stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 12:13:36 +0100] rev 4629
fix 4626:c26b4df9fc90 (#703911): use can't rely on peid since it's not an actual eid when we're creating the parent entity
Thu, 18 Feb 2010 11:08:00 +0100 [form fields] nicer behaviour of the password field: don't put internal field value on edition (triggering validation error if one validation without removing the value, due to confirmation mismatch), and don't show the field as required in such case stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 11:08:00 +0100] rev 4628
[form fields] nicer behaviour of the password field: don't put internal field value on edition (triggering validation error if one validation without removing the value, due to confirmation mismatch), and don't show the field as required in such case
Thu, 18 Feb 2010 11:06:40 +0100 minor cleanup: don't use builtin 'id' as variable name stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 11:06:40 +0100] rev 4627
minor cleanup: don't use builtin 'id' as variable name
Thu, 18 Feb 2010 10:57:50 +0100 [forms/inline] fix #703911: add new link disappears if inline box removed. Since we've the information, we must specify the target type else we get random cardinality on ambiguous relations stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 10:57:50 +0100] rev 4626
[forms/inline] fix #703911: add new link disappears if inline box removed. Since we've the information, we must specify the target type else we get random cardinality on ambiguous relations
Thu, 18 Feb 2010 10:55:41 +0100 this is not the form renderer responsability to check for update permissions. Move this to autoform editable_attributes relation stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 10:55:41 +0100] rev 4625
this is not the form renderer responsability to check for update permissions. Move this to autoform editable_attributes relation
Thu, 18 Feb 2010 10:54:50 +0100 turn default logging threshold to warning (we usually want them), and log 'no schema for eid' pb using warning instead of error, so we see them in logs but not during migration stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 10:54:50 +0100] rev 4624
turn default logging threshold to warning (we usually want them), and log 'no schema for eid' pb using warning instead of error, so we see them in logs but not during migration
Thu, 18 Feb 2010 09:26:04 +0100 pfff, sorry to keep messing with default/stable... stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 09:26:04 +0100] rev 4623
pfff, sorry to keep messing with default/stable...
(0) -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 tip