https://bugs.kde.org/show_bug.cgi?id=396559
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=396559
--- Comment #7 from Maik Qualmann ---
The scanning process is a separate task that does not block the GUI. In this
case it would help because of the locked database, with the digiKam database to
switch to a local MySQL server.
Maik
--
You are
https://bugs.kde.org/show_bug.cgi?id=396559
--- Comment #6 from IWBR ---
But isn´t there a way not to freeze the whole interface while scanning for new
items? Bug #389652 is basically a consequence of this.
Ideally, you should be able to use Digikam even if it´s scanning for new items.
Just
https://bugs.kde.org/show_bug.cgi?id=396559
--- Comment #5 from Maik Qualmann ---
A locked database is completely normal with SQLite. It is not possible to read
and write from a SQLite database at the same time, an active write action must
first be completed.
Maik
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=396559
--- Comment #4 from Ben ---
In our case the database file is local. the lock error happens nevertheless.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396559
Maik Qualmann changed:
What|Removed |Added
CC||ben.hu...@framestore.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=396559
--- Comment #2 from IWBR ---
The files (a whole folder of 400 pictures) was copied using windows explorer to
its destination.
Is this a problem that only affects SQLite? Would changing to MySQL or another
database avoid these waiting times?
Tell me
https://bugs.kde.org/show_bug.cgi?id=396559
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=396559
IWBR changed:
What|Removed |Added
CC||iwannaber...@gmail.com
--
You are receiving this mail
