Skip to content
This repository has been archived by the owner. It is now read-only.

Consider moving to databases from files for calendar data stores #438

Closed
macosforgebot opened this issue Sep 19, 2007 · 3 comments
Closed

Consider moving to databases from files for calendar data stores #438

macosforgebot opened this issue Sep 19, 2007 · 3 comments

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Sep 19, 2007

@wsanchez originally submitted this as ticket:198


File-based data store is nice and simple, but there are some cases where it's starting to bite us.

We should evaluate the feasibility of using a database per calendar, a database per calendar home, or some mix of authoritative databases (as opposed to indexes, as we have now) and some files (eg. we'll probably still want files for attachments, etc).

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Oct 28, 2008

@wsanchez originally submitted this as comment:1:⁠ticket:198


Files are a challenge in a couple of ways:

  • open/close of lots of small files adds up, and can be very expensive for reporting.
  • we mitigate this somewhat by using SQLite indexes
  • Atomicity is pretty well impossible: if I change a meeting with 100 attendees, in the current code, I'm touching 100 files. If an error occurs mid-way, we have inconsistent data which needs cleanup.

I'd also like to see that for a given meeting (UID = x), that there is one master copy of the meeting, and attendees have that master copy plus their own edits. That's possible with files as well as with a DB, but my gut feel is that it will be harder with files.

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Feb 25, 2010

@wsanchez originally submitted this as comment:2:⁠ticket:198

  • Owner changed from @wsanchez to @glyph
  • Milestone changed from CalendarServer-2.x to CalendarServer-3.x
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:3:⁠ticket:198

  • Radar deleted
  • Status changed from new to closed
  • Milestone changed from CalendarServer-3.x to CalendarServer-3.0
  • Resolution changed from to Software changed

3.0 for the win

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.