epiphany40223 / epiphany Goto Github PK

As of today, the Ecobee SQLite3 database is 193MB.

On the one hand, we want all that data. On the other hand, if it's already nearly 200MB after just a month or three, it's going to grow pretty big pretty quickly.

1. Does it matter that it's going to grow huge?
2. Should we take steps to make it not grow so huge?
   • E.g., should we have one SQLite database per month, or something?
   • And if we do that (e.g., split by month), will that make analyzing the data in the future more difficult?

@fowlerk Thoughts?

Per Jeff and @fowlerk discussions, let's use the json module to store meta data associated with the Ecobee scripts (vs. the shelve module, which we had problems running on Windows Server 2019, for some reason).

@toQhom We forgot to add code in to https://github.com/epiphany40223/epiphany/blob/master/media/windows/calendar-reservations/calendar-reservations.py to check and make sure there is no conflict on the calendar before accepting.

Additionally, I think we need to have the option for rejecting based on whether there is a conflict or not. Specifically:

• On the main Epiphany Events calendar, we'll accept events even if there are conflicts.
• On room calendars, we will not accept events if there's another event that conflicts.