Database separation for similarity searches

[Mario Frank]

Hey Gilles,

I looked at the code yesterday and it is not yet finished. I will apply
some changes to improve performance and report on it before committing.

For which release is the db separation planned? 5.9 or 6.0?

Best

Mario


Am 06.01.2018 um 17:43 schrieb Mario Frank:
> Hey Gilles,
>
> I think she was not completely finished. I will have time for digiKam
> again after this weekend. I will take a look. I've got unfinished work
> anyway.
>
> Cheers
> Mario
>
> Am 6. Januar 2018 16:16:37 MEZ schrieb Gilles Caulier
> <caulier.gilles at gmail.com>:
>
>     Note : with this commit, i sync this branch with master without
>     conflict.
>
>     https://commits.kde.org/digikam/d8511b14fd3e9c3406357858f557bdefa03d1551
>
>     Gilles
>
>     2018-01-06 16:13 GMT+01:00 Gilles Caulier
>     <caulier.gilles at gmail.com <mailto:caulier.gilles at gmail.com>>:
>
>         Hi all,
>
>         This summer, Swaty has work on database separation for
>         similarity searches. The goal was to separate the fuzzy
>         fingerprints storage from core DB to a dedicated DB. This will
>         simplify the backup and prevent to overload the core DB with
>         large data by image (around 500 bytes by fingerprints)
>
>         The work is not completed as i know. All have be done
>         in origin/gsoc17-db-sep branch from git repository.
>
>         What's the status of this code exactly ? Can we continue with
>         this implementation, or it will be better to re-start this
>         work from scratch ?
>
>         The DB separation is important for the future. Thank sin
>         advance for your feedback.
>
>         Best
>
>         Gilles
>
>
>
> -- 
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20180122/8f8c17c4/attachment.html>