mivanchenko a56a238e81 Fix: exclude cancelled bookings from the no-overlap constraint ...

bookings_no_overlap (the GiST exclusion constraint preventing
double-booking) had no WHERE clause, so a cancelled booking's old time
range stayed "occupied" forever -- permanently blocking that
resource+slot from ever being booked again, even though the booking
itself is dead. Found live: a cancelled test booking blocked a real
reschedule attempt into the same slot ("overlaps with an existing
appointment" even though nothing active was there).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-12 02:42:06 +02:00

..

app

Owner agenda: hide cancelled bookings by default, with a toggle

2026-09-12 02:33:18 +02:00

db

Fix: exclude cancelled bookings from the no-overlap constraint

2026-09-12 02:42:06 +02:00

.env.example

Owner notification webhook: Telegram re-point (#23)

2026-08-04 12:09:39 +02:00

docker-compose.yml

Owner notification webhook: Telegram re-point (#23)

2026-08-04 12:09:39 +02:00