1. 09 Nov, 2019 2 commits
  2. 06 Nov, 2019 3 commits
  3. 31 Oct, 2019 1 commit
    • louiz’'s avatar
      Split all the e2e tests in their own files · bd41bc8b
      louiz’ authored
      Some duplication is avoided, but most importantly: it’s much much cleaner,
      easier to find, functions have been cleaned up (functools.partial usages are
      now hidden), etc.
      bd41bc8b
  4. 23 Sep, 2019 2 commits
  5. 22 Sep, 2019 1 commit
  6. 18 Sep, 2019 1 commit
  7. 14 Sep, 2019 1 commit
  8. 25 Aug, 2019 1 commit
  9. 20 Aug, 2019 2 commits
  10. 04 Oct, 2018 1 commit
  11. 17 Sep, 2018 1 commit
  12. 26 Aug, 2018 1 commit
  13. 23 Aug, 2018 2 commits
  14. 27 Jul, 2018 1 commit
  15. 25 Jul, 2018 4 commits
  16. 24 Jul, 2018 1 commit
  17. 25 Jun, 2018 1 commit
  18. 19 Jun, 2018 1 commit
  19. 17 Jun, 2018 1 commit
  20. 01 Jun, 2018 1 commit
  21. 15 May, 2018 1 commit
  22. 14 May, 2018 1 commit
  23. 29 Apr, 2018 2 commits
  24. 28 Apr, 2018 2 commits
  25. 24 Apr, 2018 1 commit
  26. 13 Apr, 2018 1 commit
  27. 10 Apr, 2018 1 commit
    • louiz’'s avatar
      Use a different Date data type · 857c7d39
      louiz’ authored
      PLEASE backup your database before testing this commit, and report any
      migration issue.
      
      In postgresql, we use timestamp with timezone.
      In sqlite3 we use REAL (the date is expressed as julianday)
      
      This requires a migration of the muclogline_ table:
      In postgresql it’s pretty simple, we convert all the integer into timestamps
      
      With sqlite3, we actually rename the table, create the new one with the
      correct type, then copy everything to the new table, with a conversion
      function for the Date_ column, and then we delete the old table.
      
      fix #3343
      857c7d39
  28. 31 Mar, 2018 1 commit
  29. 26 Mar, 2018 1 commit