https://bugs.kde.org/show_bug.cgi?id=426116
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||8.1.0
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426116
--- Comment #6 from Jo ---
Hi Mario,
Sounds nice, and exactly what I'm looking for.
The only drawback is I've to edit the paths each newly added database again.
Not that it happens very often, so it might be ok. Still i see it technically
useful to im
https://bugs.kde.org/show_bug.cgi?id=426116
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #5 from Ma
https://bugs.kde.org/show_bug.cgi?id=426116
--- Comment #4 from Jo ---
Yes, I no doubt, my question wasn't to unify databases into one big and
inefficient database, but to create a kind of Digikam file that contains all
these database data, to clean up all those loose files
>You can save the d
https://bugs.kde.org/show_bug.cgi?id=426116
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #3 from Maik
https://bugs.kde.org/show_bug.cgi?id=426116
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Albums-Engine |Database
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=426116
--- Comment #2 from Jo ---
I'm talking about the database files created to monitor folder and file changes
on hd
(digikam.db, recognition.db, similarity.db, thumbnails.db, etc. ), so it'll be
the collection of albums
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=426116
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=426116
caulier.gil...@gmail.com changed:
What|Removed |Added
OS|All |macOS
--
You are receiving this mail
