1. 21 Jun, 2018 1 commit
    • Vincent Pelletier's avatar
      erp5_accounting: Give a None selection_domain instead of an empty dict. · 9d29b906
      Vincent Pelletier authored
      Otherwise, the query will include a pointless "node.uid > 0" condition
      (because internal API has no choice but to return a condition) which
      confuses the query optimiser and may lead to very suboptimal execution
      plans: a range scan of node.uid (catalog as node, node.uid=stock.node_uid)
      despite provided account uid list constraining stock.node_uid.
      9d29b906
  2. 20 Jun, 2018 2 commits
  3. 19 Jun, 2018 1 commit
  4. 18 Jun, 2018 1 commit
    • Georgios Dagkakis's avatar
      Coordinate reachability · f6c56826
      Georgios Dagkakis authored
      This Merge Request adds ```reachability_workflow``` and adds it to all Coordinate types  (Adress, Email etc.)
      so that the can be marked as ```reachable``` or ```unreachable```.
      It also adds ```coordinate_interaction_workflow```, so that when a coordinate text changes actions can be triggered.
      The default behaviour is that, when coordinate text changes for an 'unreachable' Coordinate, it is marked as reachable.
      
      We already discussed this with @jerome , but I cc @nexedi , since this can break compatibility in projects, because
      in the past Coordinates acquired ```validation_state``` by their parent document (Person, Organisation, etc).
      So now, if some code checks ```getValidationState``` (though it should be checking on the parent) for Coordinate, or searches Catalog with ```validation_state``` (though it should be ```parent_validation_state```), behaviour will change.
      
      Test Result <a href="https://nexedijs.erp5.net/#/test_result_module/20180608-2D68AF16">here</a> seems good (3 failures in UI tests that seem unrelated)
      
      
      /reviewed-on !691
      f6c56826
  5. 15 Jun, 2018 6 commits
  6. 14 Jun, 2018 13 commits
  7. 13 Jun, 2018 5 commits
  8. 12 Jun, 2018 11 commits