Skip to content

erp5
erp5
An error occurred fetching the project authors.
Switch branch/tag
  1. 23 Apr, 2020 1 commit
  3. 13 Jan, 2020 1 commit
  5. 24 Jan, 2018 1 commit
    • Vincent Pelletier's avatar
      all: Avoid trivial direct calls to {recursiveI,i}mmediateReindexObject · ab9e0f93
      Vincent Pelletier authored 
      These methods must not be called synchronously:
- they can break catalog by not being careful enough about other
  reindexations which may happen in parallel. See the serialization_tag
  mechanism for more.
- indexation gets executed in the security context of the user causing the
  call, which may lead to an indexation result different from what happens
  when indexation happens with an all-accesses user.
These lines of code (some even commented-out) give a bad example. Replace
them with safe equivalents.
      ab9e0f93
  7. 04 Sep, 2014 1 commit
  9. 03 Oct, 2012 1 commit
    • Julien Muchembled's avatar
      Simulation: splitted expand, performance improvements and bugfixes · 5c09e2e2
      Julien Muchembled authored 
      All interactions and activity tags are reviewed to fix bugs like duplicated
root applied rules, and also reduces the amount of duplicated/useless work, e.g:
- Simulation trees are not expanded anymore when simulated objects are modified.
- 'expand' activities are merged (i.e. dropped) with any other 'expand' activity
  for an ancestor.
New implementation exposes new API that hides much complexity to the developper
about activity dependencies.

By default, expand() now automatically defers any work if the current
transaction takes too long time. This method also gains a parameter to
explicitely choose when to expand, which is often important in unit tests or
solvers. In particular, when postponing work, it takes care of setting proper
activity dependencies.
- If you have any code requiring to expand everything immediately, you'll have
  to replace 'expand()' by 'expand(expand_policy="immediate")'.
- On the contrary, you should replace any 'activate().expand()' by
  'expand(expand_policy="deferred")'.
expand() still accepts activity parameters for any extra needs.

In causality workflow, 'building' state is clarified and now means
« delivery may diverge but we can't know now ». A delivery remains in draft
as long as it does not contain any movement built from simulation.
After init/clone/builder/etc. scripts used to call 'startBuilding' &
'updateCausalityState': this calls must be removed since only
SimulatedDeliveryBuilder should take care of move to 'building' state and
workflows now triggers 'updateCausalityState'.

Disguised interactions have been unhardcoded and either deleted, or moved to
appropriate interaction workflows, which have been reorganized. Those
that triggers update of portal_workflow can be easily customized or disabled.

New API:
- updateSimulation() on deliveries and subscription items. It takes care of
  creating root applied rule, expanding and reindexing parts of simulation
  trees. It somehow replaces:
  - Delivery_updateSimulation
  - Delivery_updateAppliedRule
  - Delivery.applyToDeliveryRelatedMovement
  - Delivery.updateAppliedRule
  - Delivery.expand
  - Delivery.expandRuleRelatedToMovement
  - SubscriptionItem.expand
  - SubscriptionItem.updateAppliedRule
- Delivery.localBuild() is the new way to do local building and replaces
  Delivery_expandAndBuild. Private method Delivery._localBuild replaces
  Delivery_buildOnComposedDocument.
- Simulation Movements that are being built by a builder are reindexed with
  the following tag: 'built:<delivery_path>'. Any after_path_and_method_id
  dependency against 'related_simulation_movement_path_list' and reindexing
  methods should be replaced by this after_tag.

After builder scripts used to confirm the delivery in a separate activity,
which was useless.
      5c09e2e2
  11. 04 Jun, 2012 1 commit
  13. 16 Mar, 2010 1 commit
  15. 10 Mar, 2010 1 commit
  17. 17 Nov, 2009 1 commit
    • Sebastien Robin's avatar
      - the possibility to pass --enable_full_indexing=portal_skins in · 2dd6ad08
      Sebastien Robin authored 
       order to make optimisation configuration in unit test
- isIndexable is not a property any more, it is a ConstantGetter
 instance, so it works like a property and like a method
- same thing for isPredicate, isTemplate, isDelivery... we can
 start moving using only methods.
- do not define isTemplate, isDelivery... when it is already
  available thanks to inheritance
- new methods generated for all ERP5 objects : provides[InterfaceName].
 For instance, "providesIMovement()" will return True or False for
 any ERP5 object.
- new method "is[Group]Type" generated for all ERP5 objects. The group
 here is group of portal types (like getPortalDeliveryTypeList()). So
 on any ERP5 object, you can do "isDeliveryType()", and this will
 returns True or False.
- add tests

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30704 20353a03-c40f-0410-a6d1-a30d3c3de9de
      2dd6ad08
  19. 01 Sep, 2009 1 commit
  21. 19 Aug, 2009 1 commit
  23. 12 Jun, 2009 2 commits
  25. 01 Jun, 2009 1 commit
  27. 26 Sep, 2008 1 commit
  29. 23 Sep, 2008 2 commits
  31. 06 Nov, 2007 1 commit
  33. 26 Jan, 2007 1 commit
  35. 15 Nov, 2006 1 commit
  37. 08 Sep, 2006 1 commit
  39. 18 Jul, 2006 1 commit
  41. 05 May, 2006 1 commit
  43. 25 Mar, 2006 1 commit
  45. 01 Mar, 2006 1 commit
  47. 10 Jan, 2006 1 commit
  49. 28 Oct, 2005 1 commit
  51. 27 Jun, 2005 1 commit
  53. 24 Jun, 2005 1 commit
  55. 18 Apr, 2005 1 commit
  57. 04 Feb, 2005 1 commit
  59. 13 Oct, 2004 1 commit
  61. 30 Sep, 2004 1 commit
  63. 03 Sep, 2004 1 commit
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7