Tomas DvorakandDevin 9f92a2026f fix(bookings): enforce no-overlap atomically via exclusion constraints ...

Check-then-insert left a race: two concurrent requests for the same
slot could both confirm. Migration 00014 adds three partial btree_gist
exclusion constraints mirroring resourcesCollide semantics (same
staff, same location, both-unassigned), excluding cancelled rows and
class bookings. SQLSTATE 23P01 maps to ErrBookingConflict at all three
write paths so a lost race returns a clean 409.

Validated on a local Postgres 17 container: constraint matrix at SQL
level, repo-level 23P01 detection, concurrent burst yielding exactly
one confirmed booking.

Authored By: TDvorak <[email protected]>

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-09-18 13:27:47 +02:00

..

customer_service_test.go

refactor(db): replace sqlc with handwritten pgx repos

2026-09-17 20:21:34 +02:00

customer_service.go

fix(bookings): enforce no-overlap atomically via exclusion constraints

2026-09-18 13:27:47 +02:00

lifecycle.go

fix(reminders): re-arm reminder jobs on waitlist promotion

2026-09-18 13:18:39 +02:00

service_test.go

feat(waitlist): queue position on the customer manage page

2026-09-18 13:07:06 +02:00

service.go

fix(bookings): enforce no-overlap atomically via exclusion constraints

2026-09-18 13:27:47 +02:00