1. 03 Aug, 2020 3 commits
    • Antonio Larrosa Jimenez's avatar
    • Antonio Larrosa Jimenez's avatar
      Check availability of Postgresql backend and clean a bit the code · 217fc7bd
      Antonio Larrosa Jimenez authored and Antonio Larrosa Jimenez's avatar Antonio Larrosa Jimenez committed
      Rename `areRequirementsAvailable` method to `isAvailable` and implement the
      method for DbConfigPostgresql too.
      Extract the code from `DbConfig::configuredDatabase` that selects the fallback
      to use to a new separate static method, `defaultAvailableDatabaseBackend`
      to be more clear about what that code does and simplify `configuredDatabase`.
      Now if Postgresql is expected to be used (because akonadi was built like that)
      but QPSQL is not available or the initdb/pg_ctl binaries don't exist, then we
      fallback to trying to use QSQLITE3.
      As with the `DbConfigMysql` change, if QSQLITE3 can't be used either, then
      the code will continue trying to use postgresql and fail as expected.
    • Antonio Larrosa Jimenez's avatar
      Fallback to using the QSQLITE3 driver if QMYSQL can't be used · 8240e111
      Antonio Larrosa Jimenez authored and Antonio Larrosa Jimenez's avatar Antonio Larrosa Jimenez committed
      On SUSE Linux Enterprise Desktop (SLED) with the PackageHub repository
      enabled (which provides the KDE packages) the mysql package is not available,
      so there's no mysqld, and the QMYSQL driver can't be used.
      OTOH, SUSE Linux Enterprise Server (SLES) with the same PackageHub repository
      enabled has a mariadb package available which provides the mysqld binary.
      Since the akonadi-server package for SLES and SLED is the same, we can't
      just set DATABASE_BACKEND to SQLITE at buildtime and we need to choose
      a fallback at runtime, which is what this commit implements.
      If it's the first time akonadi starts and mysql is expected to be used, this
      commit checks if it's really usable, and if it's not, it checks if the QSQLITE3 driver
      is available and if it is, we fall back to it instead of using mysql.
      Since we need to find out if a DbConfig* object can be initialized before
      it's actually initialized, I added a bool storeSettings parameter to
      DbConfig::init(QSettings &) that can be used to try the initialization
      (find out available paths, etc.) without storing anything.
      Then I added two methods DbConfigMysql::areRequirementsAvailable and
      DbConfigSqlite::areRequirementsAvailable that check if the given object
      has the system requirements available. I didn't add it to
      DbConfigPostgresql because Postgresql isn't used by default in any case.
      Also, note that this check is only done the first time akonadi starts
      when it's not configured. Once it starts with mysql or sqlite3 this
      configuration is stored and used the next times without any further
  2. 02 Jul, 2020 1 commit
  3. 10 Aug, 2018 1 commit
  4. 04 Jun, 2017 1 commit
  5. 06 Jan, 2017 1 commit
  6. 03 Jan, 2017 1 commit
  7. 13 Oct, 2016 1 commit
  8. 14 May, 2016 1 commit
  9. 27 Aug, 2014 1 commit
  10. 31 Jul, 2014 1 commit
  11. 17 Feb, 2014 1 commit
    • Daniel Vrátil's avatar
      Wrap all classes in /server to Akonadi::Server namespace · c90b946d
      Daniel Vrátil authored
      Since we now support loading of plugins, having only Akonadi namespace
      might not be enough, as plugins can easily clash (like Akonadi::TagAttribute
      from Akonadi and from kdepimlibs). It will also make it easier to differentiate
      classes once both server and client libs are in the same repo in KF5.
  12. 05 Nov, 2010 1 commit
  13. 23 Mar, 2010 1 commit
  14. 08 Jan, 2010 1 commit