Decouple calendar manager from storage provider

RESOLVED FIXED in 1.0b1

Status

Calendar
Internal Components
--
enhancement
RESOLVED FIXED
11 years ago
6 years ago

People

(Reporter: dbo, Assigned: dbo)

Tracking

unspecified
1.0b1
Bug Flags:
wanted-calendar1.0 +

Details

(Assignee)

Description

11 years ago
IMO it's a mess that the calendar management code is tied to the storage provider's schema, i.e. checking/relying on its schema version.
Effect is that it's currently not possible to register a provider (!=storage) unless at least once a storage calendar has been created. This hinders any auto configuration attempts.

IMO the calendar management code should use an own schema version.
+1

When I was doing various SQL schema updates and the "schema too new" error dialog, it seemed wrong to me that both the calendar manager/properties and the storage provider used the same schema version row.

This needs to be changed.
We might even want to reconsider if storing calendar properties in the database is the right way. It seems more logical (at least to me) to store them as preferences.
mailnews does that, and it seems to work ok there.
(Assignee)

Comment 3

11 years ago
(In reply to comment #2)
Related is bug 378754 (calendar auto config) which would possibly be obsolete if we configure calendars via prefs.
Flags: blocking-calendar0.7?
(Assignee)

Comment 4

10 years ago
I think we should first judge on pref based calendar registration (bug 403006), then this bug would be obsolete.
Depends on: 403006
Flags: blocking-calendar0.7?
(Assignee)

Updated

10 years ago
Flags: wanted-calendar0.9+
(Assignee)

Updated

9 years ago
Flags: wanted-calendar0.9+ → wanted-calendar1.0+
(Assignee)

Comment 5

9 years ago
fixed with bug 403006.
Assignee: nobody → daniel.boelzle
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
You need to log in before you can comment on or make changes to this bug.