fix: (CalDav) Delete invitation link when deleting Calendars or Events

[SebastianKrupinski]

• Resolves: When a calendar event is deleted, corresponding calendar_invitation entries are not deleted #12387

Summary

When deleting a calendar or event also delete event invitation links

[tcitworld]

We also need a repair step to purge all entries in calendar_invitations which don't match existing calendar objects.

[miaulalala]

We also need a repair step to purge all entries in calendar_invitations which don't match existing calendar objects.

Set the expiration date for those outdated links to in the past, and the CleanupInvitationTokenJob will take care of it.

https://github.com/nextcloud/server/blob/af6de04e9e141466dc229e444ff3f146f4a34765/apps/dav/lib/BackgroundJob/CleanupInvitationTokenJob.php

It will probably need modifications like

server/apps/dav/lib/BackgroundJob/DeleteOutdatedSchedulingObjects.php

Lines 30 to 34 in af6de04

	protected function run($argument): void {
	$time = $this->time->getTime() - (60 * 60);
	$this->calDavBackend->deleteOutdatedSchedulingObjects($time, 50000);
	$this->logger->info('Removed outdated scheduling objects');
	}

as to not completely crash an instance until all outdated links are deleted.

Would be a good idea to get some data from our instance too to see how many of these links exist in our database. Please ask the sysadmins to run a query for you.

[tcitworld]

In my production instance, with ~22k rows in oc_calendar_invitations and 22M rows in oc_calendarobjects, I get 2162 entries for

select count(i.id) from oc_calendar_invitations i left join oc_calendarobjects o on i.uid = o.uid where o.id is null;

[SebastianKrupinski]

In my production instance, with ~22k rows in oc_calendar_invitations and 22M rows in oc_calendarobjects, I get 2162 entries for

22M rows! wow. Can you tell how many calendar object the biggest calendar has?

[tcitworld]

Can you tell how many calendar object the biggest calendar has?

51k objects

[st3iny]

Tested and works. Code looks good, too.

[st3iny]

/backport to stable30

[st3iny]

/backport to stable29

[st3iny]

/backport to stable28

[ChristophWurst]

Looks good!

Performance wise, we can optimize the query loop a bit