Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove old scheduling objects from INBOX and oc_schedulingobjects via cron #43621

Open
miaulalala opened this issue Feb 16, 2024 · 1 comment · May be fixed by #45235
Open

Remove old scheduling objects from INBOX and oc_schedulingobjects via cron #43621

miaulalala opened this issue Feb 16, 2024 · 1 comment · May be fixed by #45235

Comments

@miaulalala
Copy link
Contributor

When a scheduling event is in the past, the scheduling event should be removed from oc_schedulingobjects and the associated ICS in the scheduling inbox should be deleted: sabre-io/dav#1138

Any FREEBUSY request checks the schedulingobjects / a users inbox). The search will be limited by a start and end date. Since there is no dedicated timestamp on each entry of the table, but instead the query is done on a text column, this is where I would expect the largest performance impact.

@miaulalala miaulalala added enhancement 1. to develop Accepted and waiting to be taken care of performance 🚀 labels Feb 16, 2024
@miaulalala miaulalala added this to the Nextcloud 29 milestone Feb 16, 2024
@miaulalala miaulalala self-assigned this Feb 16, 2024
@ChristophWurst
Copy link
Member

Query analysis of a production instance. Time span is one week.

image

SELECT
  `uri`,
  `calendardata`,
  `lastmodified`,
  `etag`,
  `size`
FROM
  `oc_schedulingobjects`
WHERE
  `principaluri` = ?

@miaulalala miaulalala linked a pull request May 8, 2024 that will close this issue
3 tasks
@ChristophWurst ChristophWurst added 2. developing Work in progress and removed 1. to develop Accepted and waiting to be taken care of labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏗️ In progress
Development

Successfully merging a pull request may close this issue.

3 participants