Exchange Data Provider for Lightning

Bug #633352
Comment #117

Comment 117 for bug 633352

Revision history for this message

In Mozilla Bugzilla #769118, Orchcond (orchcond) wrote on 2016-08-07:

#117

(In reply to Pander from comment #61)
> So a proper fix should prevent creation of duplicate entries and in a safe
> way remove any exiting duplicate entries.

Pander,

First, I should mention that I was using a Google calendar with the Provider for Google calendar add-on to create the calendar in Lightning before the bug showed up. And the event that I could not dismiss or snooze was not to be found in the Google calendar itself even though that same event showed up in Thunderbird Lightning calendar. This is what gave me the idea that the data that Lightning was using had to be coming from some other source than directly from the Google calendar itself. And that's when I tracked down the cashe.sqlite file within my Profiles, calendar-data folder.

I thought that even if I totally destroyed the cashe.sqlite it didn't matter because I could still rebuild it by starting with a fresh install of a blank Lightning calendar and use Provider (or the built-in Ligthning feature of the latest version of T-bird) to pull the data from my Google calendar back in. Plus, obviously you should backup the cashe.sqlite before you modify or otherwise tinker with it.

Actually, I thought about this a lot today and recalled that at one point, after creating a recurring weekly event with a recurring reminder, I believe that I tried to modify a single instance ("This event only") and that it might have been after this that the bug appeared. So, it may have been a bug in the Lightning add-on after all that caused it to be created, i.e., trying to modify one instance of a recurring event possibly caused duplicate entries in the cashe.sqlite database file. This should not happen, of course.

But removing duplicate events from the cashe.sqlite file makes sense as a fix to the problem. You dismiss one of the reminders, but the other one pops up and says, "Guess what? I'm still here." and recreates itself again.

I still have recurring events in my calendar that work fine and were not affected by removing the duplicates of the event that I no longer wanted. At the same time it is a simple matter to just recreate the removed recurring event in the normal way in Lightning if you still want to have it.

So, I believe the short answer to your question is that the fix should cure the "can't dismiss or snooze" a reminder bug if it is caused by duplicate entries in the cashe.sqlite database file. But if you can't find a duplicate entry in the cashe.sqlite database and are still having this problem, then it is a different bug from the one that my fix solves. But I cannot promise that duplicate events won't show up in the future from the bug that caused the duplicate events in the first place. Hope all of this helps.

(In reply to Pander from comment #61)
> So a proper fix should prevent creation of duplicate entries and in a safe
> way remove any exiting duplicate entries.

Pander,

First, I should mention that I was using a Google calendar with the Provider for Google calendar add-on to create the calendar in Lightning before the bug showed up. And the event that I could not dismiss or snooze was not to be found in the Google calendar itself even though that same event showed up in Thunderbird Lightning calendar.  This is what gave me the idea that the data that Lightning was using had to be coming from some other source than directly from the Google calendar itself. And that's when I tracked down the cashe.sqlite file within my Profiles, calendar-data folder.

I thought that even if I totally destroyed the cashe.sqlite it didn't matter because I could still rebuild it by starting with a fresh install of a blank Lightning calendar and use Provider (or the built-in Ligthning feature of the latest version of T-bird) to pull the data from my Google calendar back in.  Plus, obviously you should backup the cashe.sqlite before you modify or otherwise tinker with it.

Actually, I thought about this a lot today and recalled that at one point, after creating a recurring weekly event with a recurring reminder, I believe that I tried to modify a single instance ("This event only") and that it might have been after this that the bug appeared.  So, it may have been a bug in the Lightning add-on after all that caused it to be created, i.e., trying to modify one instance of a recurring event possibly caused duplicate entries in the cashe.sqlite database file. This should not happen, of course.

I still have recurring events in my calendar that work fine and were not affected by removing the duplicates of the event that I no longer wanted.  At the same time it is a simple matter to just recreate the removed recurring event in the normal way in Lightning if you still want to have it.

So, I believe the short answer to your question is that the fix should cure the "can't dismiss or snooze" a reminder bug if it is caused by duplicate entries in the cashe.sqlite database file.  But if you can't find a duplicate entry in the cashe.sqlite database and are still having this problem, then it is a different bug from the one that my fix solves. But I cannot promise that duplicate events won't show up in the future from the bug that caused the duplicate events in the first place.  Hope all of this helps.