digiKam with another database backend than SQLite

Last summer I saw bug #127321 an thought, this can be done by me (partly at least).
After some (successful) prototypic implementation, most of the time where spent into smooth integration in the existing
project:

  • adding a solution for migrating from SQLite to MySQL and vice versa
  • add possibility to start an own database server
  • and bug fixing...

Because only a few persons trying out this work (which resides atm. in a dedicated branch), the most bugs are possible undiscovered.


This is a companion discussion topic for the original entry at https://www.digikam.org/news/2010-03-22_digikam_with_another_database_backend_than_sqlite/