https://bugs.kde.org/show_bug.cgi?id=511011
--- Comment #2 from Matt P. <[email protected]> --- Hello Gilles, I think I understand what you are saying, but this must happen during a small phase of initialisation only. If two instances of the program are started "slowly" one after the other, nothing happens. Let alone that if that "read / write blockage" on the database would be through the whole session with Digikam, it would not be possible to use Digikam from e.g. two different PCs at the same time ???? (the scenario that I am trying to build, and which is depicted in DigiKams documentations under "Network share" (albeit I could not find a clear statement in the docs that Digikam is fully designed as a multi-user environment). I just wanted to propose that the error handling in this case could be enhanced a bit, e.g. by re-trying the "offending" alter table or giving a clear indication of e.g. "database in use for setup - please retry later" instead of this "insufficient rights" message, which I find pretty misleading. Best, Matt. -- You are receiving this mail because: You are watching all bug changes.
