1. 25 Feb, 2021 1 commit
    • Jérome Perrin's avatar
      accounting: fix grouping option of GL when running in deferred mode · e6555db4
      Jérome Perrin authored
      This omit_grouping_reference key was not set as selection parameters, so
      Node_getAccountingTransactionList could not find it in selection when running
      in deferred mode.
      
      In non deferred mode, it was working, because selection is set with values from
      request and it was same request, but deferred style uses activities, so it's
      different requests.
      e6555db4
  2. 24 Feb, 2021 1 commit
  3. 23 Feb, 2021 4 commits
  4. 22 Feb, 2021 1 commit
    • Jérome Perrin's avatar
      l10n_fr: fix duplicate "Exporter" action name · d743396c
      Jérome Perrin authored
      On documents, we have an "Export" action for OOoDocument_viewConvertDialog.
      When erp5_ods_style is installed, "Export to Spreadsheet" is added as a global
      action. Both these actions were translated as "Exporter" in french, which is
      confusing and a bit incorrect.
      Use a proper, different translation for "Export to Spreadsheet"
      d743396c
  5. 19 Feb, 2021 1 commit
  6. 18 Feb, 2021 1 commit
  7. 17 Feb, 2021 2 commits
  8. 16 Feb, 2021 1 commit
  9. 15 Feb, 2021 9 commits
  10. 12 Feb, 2021 4 commits
  11. 10 Feb, 2021 4 commits
  12. 09 Feb, 2021 1 commit
    • Vincent Pelletier's avatar
      CMFActivity: Simplify validation queries further. · e4273c58
      Vincent Pelletier authored
      The query planner does not seem to notice that we are trying to know if
      any row exists matching a set of dependency values, and it keeps scanning
      multiple row for each value - which is unproductive.
      So split dependency queries from (pseudo-code)
        WHERE <column{,s}> IN <values{, pairs}>
      to unions of
        WHERE <column{,s}> = <value{, pair}> LIMIT 1
      which produces query plans which do stop immediately when finding a
      candidate row.
      On a serialization_tag query with 40 values and real-world indexations,
      this reduces the number of rows scanned by mariadb from 500 (<10%
      efficiency) to 40 (100% efficiency).
      The produced SQL is significantly larger (~3x, around 500kB on
      real-world sample data, but may vary a lot depending on value length),
      but if this has any effect is is more than compensated by the improved
      query plan efficiency.
      e4273c58
  13. 08 Feb, 2021 3 commits
  14. 05 Feb, 2021 3 commits
  15. 04 Feb, 2021 4 commits