Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

usage_data_spec.rb

  • Z.J. van de Weg's avatar
    e7d12a70
    Add in_review_folder to usage ping · e7d12a70
    Z.J. van de Weg authored
    As its hard to reliably check how many review apps there are on the
    clients machine, we start by checking where the type is `review`. This
    means the folder is called that way. This will lead to a seq
    scan on the table. However, this is done once a week, so the benefit of
    adding an index seems not to apply here.
    e7d12a70
    History
    Add in_review_folder to usage ping
    Z.J. van de Weg authored
    As its hard to reliably check how many review apps there are on the
    clients machine, we start by checking where the type is `review`. This
    means the folder is called that way. This will lead to a seq
    scan on the table. However, this is done once a week, so the benefit of
    adding an index seems not to apply here.