Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 09:52:38 +0100] rev 4652
restore 3.5 compat for date functions moved to lgc.date in 3.6 (closes #716055)
Nicolas Chauvat <nicolas.chauvat@logilab.fr> [Mon, 22 Feb 2010 19:25:04 +0100] rev 4651
[devtools/fill] fix date generation and its test
Nicolas Chauvat <nicolas.chauvat@logilab.fr> [Mon, 22 Feb 2010 18:22:54 +0100] rev 4650
typo: capitalize migration confirmation messages
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 19 Feb 2010 15:12:46 +0100] rev 4649
[views/deleteconf] remove action ppty (useless & clashes with form attr, replace buggy non_final_entity selector with implements workaround
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Feb 2010 12:53:35 +0100] rev 4648
merge
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Feb 2010 10:12:33 +0100] rev 4647
[workflow] fix potential destination for go back transition
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Feb 2010 10:04:24 +0100] rev 4646
[workflow] finish refactoring introduced by 021035b9a7ab for 'go back' transition:
* fix SubWorkflowTransition.destination() prototype (must now take an entity as argument)
* fix the change state for to give the entity to the transition's destination() method
* we need a new method to draw workflow since we've no entity to give and 'go back'
transition usually go back to multiple states
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Feb 2010 09:37:03 +0100] rev 4645
deprecate Transition.set_transition_permissions in favor of set_permissions (after all we know we're on a transition entity)
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Feb 2010 09:36:26 +0100] rev 4644
introduce 'go back' transition: transition without destination state will go to the state we were coming from
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Feb 2010 09:34:14 +0100] rev 4643
fix optimisation with super session that may lead to integrity loss
at some point I've decided to stop ensuring ?1 cardinality was respected
when adding a new relation using a super session, to avoid the cost of
the delete query. That was yet discussable because it introduced unexpected
difference between execute and unsafe_execute, which is imo not worth it.
Also, now that rql() in migration script default to unsafe_execute, we
definitly don't want that implicit behaviour change (which already cause
bug when for instance adding another default workflow for an entity type:
without that fix we end up with *two* default workflows while the schema
tells we can have only one.
IMO we should go to the direction that super session skip all security
check, but nothing else, unless explicitly asked.
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 19 Feb 2010 12:14:35 +0100] rev 4642
[auto/inline forms] reallow nested inline forms #703910
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 15:42:29 +0100] rev 4641
[reledit] fix #713217: reledit doesn't check 'update' permission on attributes
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 15:42:09 +0100] rev 4640
fix dumb name error
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 14:27:00 +0100] rev 4639
cleanup internal forms parameters in postlogin
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 18 Feb 2010 14:07:56 +0100] rev 4638
grmmbl, bad resolve