1. 09 Sep, 2024 2 commits
  2. 05 Sep, 2024 1 commit
  3. 03 Sep, 2024 5 commits
  4. 31 Aug, 2024 1 commit
  5. 30 Aug, 2024 2 commits
  6. 28 Aug, 2024 1 commit
  7. 27 Aug, 2024 1 commit
  8. 26 Aug, 2024 4 commits
  9. 16 Aug, 2024 1 commit
  10. 14 Aug, 2024 1 commit
  11. 13 Aug, 2024 1 commit
  12. 12 Aug, 2024 2 commits
  13. 07 Aug, 2024 2 commits
  14. 06 Aug, 2024 1 commit
  15. 02 Aug, 2024 2 commits
  16. 01 Aug, 2024 4 commits
  17. 30 Jul, 2024 1 commit
  18. 29 Jul, 2024 4 commits
  19. 25 Jul, 2024 2 commits
  20. 23 Jul, 2024 2 commits
    • Rafael Monnerat's avatar
      ERP5Type: Include OFSFolder2._cleanup method · 6e6eb5f0
      Rafael Monnerat authored
        This aims to add compatibility with BTreeFolder2 API, even it is not
        required. Since some checkConsistency may call self._cleanup() regardless
        expecting that the folder is a [H]BTreeFolder2 always.
      
        This was detected when a post upgrade constrant was included to
        portal_categories
      6e6eb5f0
    • Jérome Perrin's avatar
      core: handle price 0 or None in Inventory API · 2c525e57
      Jérome Perrin authored
      The methods used in indexing did not make a difference between the case
      where the price is None (ie. price is not set) or where the price is
      set to 0 - in both cases this was saved as NULL in stock.total_price
      column. This is incorrect, we need to keep the distinction between
      these two cases also for inventory calculation.
      We had some places where we select IFNULL(stock.total_price, 0) to work
      around this, we don't plan to change the existing ones for now, but
      while discussing on nexedi/erp5!1974
      we concluded that a newly idenfified case of a problem consequence of
      these NULL should be handled by fixing the indexation. To benefit from
      the fix, impacted instances will have to reindex documents present in
      the stock table with stock.total_price is null.
      2c525e57