[digikam] [Bug 146865] MYSQL : networked and multi-users database backend
https://bugs.kde.org/show_bug.cgi?id=146865 --- Comment #14 from Maik Qualmann --- The Comment 13 is posted incorrectly here. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146865] MYSQL : networked and multi-users database backend
https://bugs.kde.org/show_bug.cgi?id=146865 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #13 from Maik Qualmann --- Please note that the database connection test is only a test of the database, username and password. The tables are created much later after the first start dialog. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146865] MYSQL : networked and multi-users database backend
https://bugs.kde.org/show_bug.cgi?id=146865 --- Comment #12 from Kjetil Kjernsmo --- (In reply to Dan Fallon from comment #11) > While this seems like a cool idea, it seems like you didn't > read the rest of the thread before necro'ing this feature request to promote > a project you work on... > > https://solidproject.org/team#kjetil-kjernsmo With all due respect, Dan, but if you read the thread, you'd see that I was participating in this thread 15 years ago, and at that time, there were several who were open to the consideration that using RDF might be the right way to implement the use cases behind this issue. Solid basically provides the technical infrastructure to use RDF this way. I was using Digikam with a collection on an NFS share when this issue was created, and with a remote MySQL database for the last decade. Recently, I have set up MySQL so that my daughter can use Digikam on a different machine, but she hasn't done it a lot and certainly not concurrently with me. I am aware that this can be done right now, but for more advanced use cases, I would probably look to other technologies. I think your comment was rather undue, as my comment was a follow-up from the discussion that happened 15 years ago. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146865] MYSQL : networked and multi-users database backend
https://bugs.kde.org/show_bug.cgi?id=146865 Dan Fallon changed: What|Removed |Added CC||dan...@fallon.io --- Comment #11 from Dan Fallon --- (In reply to Kjetil Kjernsmo from comment #10) > This is now becoming possible within the Solid Project, > https://solidproject.org/ . We recently published the 0.9 version of the > protocol spec: > https://solidproject.org/TR/protocol Kjetil, I believe this feature request was requesting the ability to have multiple users work on a collection at the same time. In a studio setting, for example, you would want multiple editors to be able to access photos from a recent shoot to expedite the tagging and rating of photos from a recent photoshoot. For a home user, alternatively, they may want to have a photo library stored on network attached storage but have the freedom to edit from multiple computers. It also seems like *parts* of this have been implemented--excepting some caveats regarding simultaneous updates not refreshing the UI of other users. Might be worth closing this in favor of a newer ticket that better reflects the current state of things. see this article from 2018 about migrating your digikam database to MySQL and a NAS: https://www.digikam.org/news/2018-10-20_digikam_nas_mariadb/ and this documentation about how to handle a non-sqlite backend: https://docs.kde.org/trunk5/en/digikam-doc/digikam/using-setup.html#using-setup-database and this fixed bug-report about using a separate thumbnail database: https://bugs.kde.org/show_bug.cgi?id=297922 and this still open one about absolute paths being stored in the database: https://bugs.kde.org/show_bug.cgi?id=275261 (In reply to Kjetil Kjernsmo from comment #10) > This is now becoming possible within the Solid Project, > https://solidproject.org/ . We recently published the 0.9 version of the > protocol spec: > https://solidproject.org/TR/protocol solidproject seems better suited to replicating the feature-set of a photo library like google photos. Allowing users to share photos/albums with a larger audience. While this seems like a cool idea, it seems like you didn't read the rest of the thread before necro'ing this feature request to promote a project you work on... https://solidproject.org/team#kjetil-kjernsmo -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146865] MYSQL : networked and multi-users database backend
https://bugs.kde.org/show_bug.cgi?id=146865 Kjetil Kjernsmo changed: What|Removed |Added CC||kje...@kjernsmo.net --- Comment #10 from Kjetil Kjernsmo --- This is now becoming possible within the Solid Project, https://solidproject.org/ . We recently published the 0.9 version of the protocol spec: https://solidproject.org/TR/protocol The way this could be done on Solid is to create an add-on that it is a Solid client. That client has to have a concept of users and authorization policies, but as a first iteration, it could be done as simple as "just me" and "everyone else", that would still be useful, I think. The images themselves would be PUT to the server, and the metadata would be written along with it in what is in Solid an auxiliary resource, specifically a Resource Description. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146865] MYSQL : networked and multi-users database backend
https://bugs.kde.org/show_bug.cgi?id=146865 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database-Multiusers |Database-Media -- You are receiving this mail because: You are watching all bug changes.
