If you could add to each table: * owner_id , it could be digikam until a later time that it could/would be upgraded to actual users * group_id, it could be digikam until a later time that it could/would be upgraded to actual groups * location, it could be null until used * date & time of last add/edit Then most of the multi-user stuff could be done by mysql/mariadb: the record locking, the reads, the writes... Then as you dedicate more resources, things could be integrated within DK at later time to make it more transparent.
Created attachment 116746 [details] initiating mailing list discussion: digiKam-users] Multi-user digiKam setup?
Comment on attachment 116746 [details] initiating mailing list discussion: digiKam-users] Multi-user digiKam setup? >http://digikam.1695700.n4.nabble.com/digiKam-users-Multi-user-digiKam-setup-td4707375.html
Created attachment 116747 [details] supporting discussion: [digiKam-users] Use digiKam with a NAS and MariaDB
There is even some good documentation, would say it is feasible: MySQL: can I implement row-level AND column level security? https://stackoverflow.com/questions/31925882/mysql-can-i-implement-row-level-and-column-level-security Protect Your Data: Row-level Security in MariaDB 10.0 https://mariadb.com/resources/blog/protect-your-data-row-level-security-in-mariadb-10-0/ and some supporting documentation: Ten Tips on How to Achieve MySQL and MariaDB Security https://severalnines.com/blog/ten-tips-how-achieve-mysql-and-mariadb-security MySQL Table and Column Level Permissions. https://support.chartio.com/knowledgebase/mysql-table-level-permissions Dynamic Columns Tutorial – Part 1: Introduction https://mariadb.com/resources/blog/dynamic-columns-tutorial-part-1-introduction/
it was said that "The multi users setup require severals works in digiKam database interface." I'm wondering if the new plug-in model would allow realizing this request, e.g. by - intervene SQL queries to a NAS based database - do authentication against e.g. an LDAP server
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
To te KDE team ! Please DO NOT CLOSE FILE automatically file from an active project !!! We are human, and we don't need help from a stupid robot. Gilles Caulier
HAllo Gilles, you said in brief the follwoing: > A multi users setup require severals works in digiKam database interface. > It requires a remote database with a lock or versioing mechanism to prevent concurrents access to the contents. > First would only allow to open a database record in RW for the first user and in Read only for all others. > This less powerful but this simplify the workflow to manage. > Otherwise you need versionning system to cope with version created by different users. I reckon the most of us could life with that altough secons has way more chamre :) Syv comment sounds simple but cannot tell if that solves anything. Can we get any feedback on this? @Syv could you outline your approach in a more detailed fashion.