[Kde-pim] Collections without remoteId abort imap sync

[Shaheed Haque]

Hi Kevin,

I hope we all agree that having bad stuff linger in the database is
bad in general, and is clearly causing significant misbehaviour.

So, if the simplistic solution I suggested in not viable, we should
either find some other combination of values that is, or define one. I
obviously don't know the schema well enough to say what that should
be, but maybe a rev value of -1, or even a new column? A multi-column
solution might need a pre-commit trigger (or a purge on startup).

Thanks, Shaheed

2012/2/19 Kevin Krammer <kevin.krammer at gmx.at>:
> On Sunday, 2012-02-19, Shaheed Haque wrote:
>> (I also have database entries in this state,)
>>
>> Is it possible to add a "not NULL" constraint to the database for
>> remoteId? That would prevent such breakages...but then again, I don't
>> know what our backends support. If that is NOT available, then perhaps
>> at startup, all records which are in this state could be purged (with
>> appropriate logging) since AFAICS, no resource can use items in this
>> state?
>
> Collections added by non-resource clients will have an empty remoteId until
> the respective resource has processed tha collectionAdded request.
>
> Cheers,
> Kevin
>
> --
> Kevin Krammer, KDE developer, xdg-utils developer
> KDE user support, developer mentoring
>
> _______________________________________________
> 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/
_______________________________________________
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/