[digiKam-users] digikam git version , strange 'Tags' tag

[leoutation at gmx.fr]

On 2/8/19 3:22 PM, leoutation at gmx.fr wrote:
> On 2/8/19 3:10 PM, Gilles Caulier wrote:
>>
>>
>> Le ven. 8 févr. 2019 à 14:00, <leoutation at gmx.fr 
>> <mailto:leoutation at gmx.fr>> a écrit :
>>
>>     On 2/7/19 10:37 PM, leoutation at gmx.fr <mailto:leoutation at gmx.fr> 
>> wrote:
>>      > I don't know if it's safely possible to edit metadata in mariadb
>>      > database  with a tool. Then, with Digikam, i could update from
>>     database
>>      > to .xmp images metadata.
>>     I find digikam solution to update .xmp: sync from database to 
>> metadata.
>>     After that, I launched "scan for new item", it took about 30 minutes
>>     then displayed "no active" process. This message is wrong because
>>     digikam processes were active in the background (hard drive an cpu)
>>     during more than an hour an half after the "official" end.
>>
>>
>> yes, the bug is know...
>>
>> And in fact it's not a bug. Few year ago, Marcel has implemented this 
>> feature, to scan collection in background. It's done in too stages :
>>
>> 1/ scan albums without contents and register new entries in DB. This 
>> is done with progress manager.
>> 2/ scan one by one all albums and register contents  in DB. This is 
>> done in low level background.
>>
>> Gilles Caulier
> The problem is that the low level background nearly freezes computer.
> In another hand, the background progresses is very quick after the first 
> scan...
> 
Mistake -> Understand in my bad english: "In another hand, the 
background *processes* are very quick after the first
scan"

-- 
Maderios