[Digikam-devel] [Bug 127321] allow use of other database backends such as postgres and mysql

[Geert Janssens]

https://bugs.kde.org/show_bug.cgi?id=127321





--- Comment #6 from Geert Janssens <info kobaltwit be>  2009-04-06 23:39:33 ---
Thinking of multi-user support a bit further, just having a real rdbms won't
suffice. The current db backend in 0.10 holds information on local as well as
remote image collections. Obviously, local collections are not shared among
multiple users on multiple PC's.

So a more general approach could have a separate db per image collection,
stored in the root album path of the collection (or in a real rdbms).

This would allow digikam to access only those databases relevant for the image
collections that are configured on each particular machine for each user.

An example with numbers:

Suppose we have a network of 2 PCs (PC A and PC B) and one server (Server).
PC A has holds one local collection, LCollA (L stands for local)
The same for PC B: LCollB
On the server are two image collections NCollC and NCollD (N stands for
network) which are exported over nfs. NCollC will be accessed both from PC A
and PC B, while NCollD is only accessed from PC B.

Assuming each collection has got its own database, this could be configured
easily. LCollA and LCollB could continue to use SQLite as they are only
accessed locally by one user. NCollC should use MySQL (or any other networked
rdbms), as that would allow simultaneous access from PC A and PC B. NCollD can
be configured either via SQLite or MySQL as only PC B would access it. MySQL
might be preferred here, because nfs doesn't always properly implement the
locking mechanism used by SQLite, which could lead to database corruption (not
in this particular use case, as only one PC would access it, so there is no
locking issue).

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.