[Digikam-devel] [Bug 137694] New: Allow album pictures to be stored on network devices
Havard Bjastad
havard at tracetracker.com
Tue Nov 21 19:37:14 GMT 2006
------- 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=137694
Summary: Allow album pictures to be stored on network devices
Product: digikam
Version: 0.8.2
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: digikam-devel kde org
ReportedBy: havard tracetracker com
Version: 0.8.2 (using KDE KDE 3.5.5)
Installed from: Ubuntu Packages
OS: Linux
Tempting to file this as a bug, but I'm sure the developers will classify it as a feature request...
This is related to the following issues:
http://bugs.kde.org/show_bug.cgi?id=116252 : failed to update db on nfs shares
http://bugs.kde.org/show_bug.cgi?id=118543 : enable-nfs-hack no longer works
http://bugs.kde.org/show_bug.cgi?id=122516 : Album Path cannot be on Network device (Unmounted)
http://bugs.kde.org/show_bug.cgi?id=121005 : digikam won´t start when the album-path stays on nfs-volume
http://bugs.kde.org/show_bug.cgi?id=129437 : wish: Album could point to network path. Now it's impossible to view photos from shared network drive.
http://bugs.kde.org/show_bug.cgi?id=134594 : WISH: Independent database backend support for increased usability (MySQL/PostgreSQL etc)
The frequent answer seems to be, read http://www.sqlite.org/faq.html#q7
Now, as an end user, I care little or none about the backend(s) used by digikam. All I want, is to be able to store my pictures on a network drive, so other machines can access the same picture collection.
I understand that digikam keeps a database of the pictures, and that this database is now in sqlite. However, it should be REALLY EASY to provide e.g. a command-line option to store the database file in the user's home directory (even if the pictures themselves are on a network drive). This simple change should take care of the user's need, without requiring the developers to rewrite the database backend (which, obviously, is a major undertaking).
More information about the Digikam-devel
mailing list