[Digikam-devel] [Bug 134594] New: WISH: Independent database backend support for increased usability (MySQL/PostgreSQL etc)

[Halim I]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=134594         
           Summary: WISH: Independent database backend support for increased
                    usability (MySQL/PostgreSQL etc)
           Product: digikam
           Version: 0.9.0-beta2
          Platform: Slackware Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: yallaone gmail com


Version:           0.9.0-beta2 (using KDE KDE 3.5.4)
Installed from:    Slackware Packages
OS:                Linux

digikam currently is very closely linked to sqlite. This works well for small installations, but is beginning to cause a wider range of problems for future scalability and usability.

Thus I would like to re-initiate the debate on making digikam database agnostic, allowing others to write an optional mysql (or postgresql) plugin for use in addition to default sqlite. This similar to the approach taken by the amarok development team.

More and more users store/share their images on NFS volumes which does not work with sqlite, and while sqlite blames NFS implementation in linux kernel, the end result is that digikam does not function in NFS environments. The use of auto-mounted NFS home directories grow, and in multi-user scenarios such as families wanting access to the photo album from multiple users it simply doesn't work, even with the --enable-nfs-hack option

Storing data in a mySQL database makes easier access for web frontends so that albums complete with comments and data can be shared over the web

Future integration with other applications, such as for instance mythtv. Users don't want to watch pictures just on their PC anymore, but also on the TV. By having a flexible database approach, it is easier for mythtv/freevo developers to access the already classified data from digikam and showing them on the TV. Thus enabling increased KDE inter-application interaction.

Once again I realize this has been discussed earlier, but it seems to have always been very quickly dismissed as "not going to happen". Would it be possible to bring this up for discussion and if possible explore positive and negtive consequences of this?

Thanks for reading!