1. 08 Dec, 2023 - 1 commit
  2. 05 Dec, 2023 - 1 commit
  3. 24 Nov, 2023 - 1 commit
  4. 07 Nov, 2023 - 1 commit
  5. 03 Nov, 2023 - 1 commit
  6. 23 Oct, 2023 - 2 commits
  7. 19 Oct, 2023 - 1 commit
  8. 18 Oct, 2023 - 1 commit
  9. 17 Oct, 2023 - 1 commit
  10. 16 Oct, 2023 - 1 commit
  11. 04 Oct, 2023 - 1 commit
  12. 03 Oct, 2023 - 1 commit
  13. 29 Sep, 2023 - 1 commit
  14. 26 Sep, 2023 - 1 commit
    • Andrea Gianarda's avatar
      [Table Cloning] · 5e29f7d5
      Andrea Gianarda authored
          - SQLite doesn't allow to modify contraints of tables therefore a
          workaround to do so is to recreate the table from scratch.
          The old table is therefore cloned and the values are copied tot he newly
          created table.
          The cloning is done through the CREATE statement specifying the type of
          every column in order to keep it unchanged. If we were to clone and
          populate the table in one line using query "CREATE TABLE IF NOT EXISTS
          clone AS SELECT * FROM original", we might incur in a data type change.
          For example DATE columns are converted to NUM column in the clone table.
          The cloned table is populated using the INSERT statememnt and then the
          old table can be deleted.
          A new table with the desired contraints is then created and populated
          one line at a time or in one query.
      
          [MainDb]
          - Catch soci exception in the init or updateSchema function and
          pass them on to the calling function to be handled.
          - Make MainDb::isInitialized() return FALSE if the database
            initialization failed
          - In AbstractDb::connect(), catch soci exception and reset DB session if
            they are of type invalid_staement or constraint_violation as an attempt to reconnect to the database won't fix the issue.
          - After initializing the database, clean up clone tables in a separate
            SQL statemment to avoid the following error
            'sqlite3_statement_backend::loadOne: disk I/O error while executing "<statement>"'
      
          [MainDbTester]
          - Verify that the database has been correctly initialized
          - Do not attempt to retrieve data if the database has not been correctly
            initialized
      5.2.108
      5e29f7d5
  15. 22 Sep, 2023 - 2 commits
  16. 21 Sep, 2023 - 1 commit
  17. 20 Sep, 2023 - 1 commit
  18. 19 Sep, 2023 - 2 commits
  19. 18 Sep, 2023 - 3 commits
  20. 15 Sep, 2023 - 1 commit
  21. 14 Sep, 2023 - 1 commit
  22. 12 Sep, 2023 - 2 commits
  23. 08 Sep, 2023 - 1 commit
  24. 05 Sep, 2023 - 2 commits
  25. 01 Sep, 2023 - 1 commit
  26. 24 Aug, 2023 - 1 commit
  27. 23 Aug, 2023 - 2 commits
  28. 22 Aug, 2023 - 1 commit
  29. 21 Aug, 2023 - 1 commit
  30. 09 Aug, 2023 - 1 commit
  31. 02 Aug, 2023 - 1 commit
  32. 28 Jul, 2023 - 1 commit
    • Julien Wadel's avatar
      Crash on wasapi: · d11ee80e
      Julien Wadel authored
      Fix crash on logging error
      
      Default parameters:
      When creating account parameters from a configuration, avoid to set default parameters from the proxy defaults. They should already be used on the creation of parameters. Using proxy defaults avoid to overwrite explicitly unused fields.
      5.2.94
      d11ee80e