Booking an appointment no longer fails on an untyped null in the conflict check (SITP TP23 live smoke)

Shipped

October 18, 2026 at 9:47 PM UTC

Author

Kamo

Commit

340abbe

findConflicts' (:excludeId IS NULL OR a.uid <> :excludeId) with a null UUID is an untyped parameter on Postgres/Yugabyte ('could not determine data type of parameter $5'), so every new booking answered 500 (the UI never sends a uid either). A new booking excludes the all-zero id, as findPossibleDuplicates already does.