[Kde-pim] Re: Nepomukfeeders duplicate all data

[Christian Mollekopf]

On Tue, 10 May 2011 18:35:32 +0200, Christian Mollekopf  
<chrigi_1 at fastmail.fm> wrote:

> On Tue, 10 May 2011 16:36:27 +0200, Christian Mollekopf
> <chrigi_1 at fastmail.fm> wrote:
>
>> Hi,
>>
>> as already mentioned previously there is a problem with the nepomuk fast
>> classes in the feederagents.
>>
>> Unfortunately this affects all nepomuk-feeders we have and causes them  
>> to
>> duplicate all properties (summary, description, icon, etc.),
>> everytime the akonadi item is updated.
>>
>> I think this is a rather critical issue and has to be fixed for the  
>> first
>> release.
>>
>> As a quick fix i propose that we simply remove the old statement  
>> directly
>> using:
>>
>> Soprano::Model::removeAllStatements( resUri, propUri, Soprano::Node() );
>>
>> before adding the new statement using the NepomukFast classes.
>>
>
> I revise my proposal, we should just use the normal Resource api, at  
> least
> for the calendar and contacts feeders.
> Especially the contacts feeder has loads of addProperty calls and i
> believe it would be easier to just switch the whole classes to
> Nepomuk::Resource. (Nepomuk::Resource is supposed to check if the value  
> is
> already existing and avoid the duplication)

Of course that doesn't work because of the graph we set...
(Resource constructor doesn't take a graph)

>
> The email feeder would probably suffer the most from the reduced
> performance, and has the base classes copied anyways,
> so we can easily fix the few addProperty calls with a
> Soprano::Model::removeAllStatements( resUri, propUri, Soprano::Node() );
> call.
>
> If we could even postpone the release of some of these feeders until the
> dms is available, even better.
>
>>
>> Of course that is ugly as hell, but at least we don't fill the nepomuk
>> database with loads of duplicated info.
>>
>> But we will need a proper replacement using the new  
>> DatamanagementService
>> which will be in kde-runtime as of 4.7,
>> which means replacing the usage of the NepomukFast classes with the DMS.
>>
>>
>> If there are no objections I will start fixing the existing feeders with
>> the aforementioned workaround.
>>
>> Cheers,
>>
>> Chris
>> _______________________________________________
>> KDE PIM mailing list kde-pim at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-pim
>> KDE PIM home page at http://pim.kde.org/
>
>


-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/