Delete findConflictingEvents, which never returned a row

Ya

26 Agosti 2026, 06:22 UTC

Mwandishi

Kamo

Ahadi ya

9dc9415

Four independent defects, any one of which emptied the result set: it filtered e.user.id while both callers pass a member id and the two columns never coincide; e.id != :excludeEventId is UNKNOWN when the parameter is null, which is every new event; e.status != 'cancelled' dropped NULL-status rows the same way; and it had no isActive filter. It also missed meetings other people booked the member into. findBusyForMemberInRange already answers this correctly and now has both callers.