1. 07 Feb, 2018 3 commits
  2. 06 Feb, 2018 4 commits
  3. 05 Feb, 2018 5 commits
  4. 03 Feb, 2018 2 commits
  5. 02 Feb, 2018 9 commits
  6. 01 Feb, 2018 5 commits
  7. 26 Jan, 2018 2 commits
  8. 25 Jan, 2018 5 commits
  9. 24 Jan, 2018 2 commits
  10. 23 Jan, 2018 1 commit
    • Jan Provaznik's avatar
      Use limit for search count queries · 090ca9c3
      Jan Provaznik authored
      Search query is especially slow if a user searches a generic string
      which matches many records, in such case search can take tens of
      seconds or time out. To speed up the search query, we search only for
      first 1000 records, if there is >1000 matching records we just display
      "1000+" instead of precise total count supposing that with such amount
      the exact count is not so important for the user.
      
      Because for issues even limited search was not fast enough, 2-phase
      approach is used for issues: first we use simpler/faster query to get
      all public issues, if this exceeds the limit, we just return the limit.
      If the amount of matching results is lower than limit, we re-run more
      complex search query (which includes also confidential issues).
      Re-running the complex query should be fast enough in such case because the
      amount of matching issues is lower than limit.
      
      Because exact total_count is now limited, this patch also switches to
      to "prev/next" pagination.
      
      Related #40540
      090ca9c3
  11. 22 Jan, 2018 1 commit
  12. 18 Jan, 2018 1 commit