[Kde-pim] Collections without remoteId abort imap sync

[Shaheed Haque]

(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?


On 19 February 2012 10:14, Wolfgang Rohdewald <wolfgang at rohdewald.de> wrote:
> Am Sonntag, 19. Februar 2012, 11:08:17 schrieb David Faure:
>> Of course I could just clean up my SQL table from such ghost collections,
>> but  I suppose a proper recovery code path would be more useful for other
>> users in the same situation who don't have the opportunity of spending a
>> weekend in Osnabrueck to get such answers about their problems
>
> that also happened to me with a lot of folders when I first imported all
> into the new database. I remember having seen empty remoteIds for those
> in the data base.
>
> that was not with IMAP (never used that) but with normal maildir.
>
> IIRC, I then created new folders, moved messages, deleted old folders,
> renamed new to old.
>
> A fix for that would have saved me quite a few hours.
>
> --
> Wolfgang
> _______________________________________________
> 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/