mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-20 02:56:10 +00:00
e8f808b67f
The booking body is not schema-checked, so day_id, end_day_id, place_id, assignment_id, accommodation_id and the create_accommodation ids can arrive as any string. The reference guards passed them to SQL as they came. SQLite compares '0x5', '5e0' or 'abc' against an integer id and matches nothing (or, for '5e0', the row), so the guard answered "Unknown reference". Postgres refuses the cast on 14 and 15 and reads hex as a number from 16 on, so the same body answered a 500 on one major and reached a real row on another; the Postgres 14 lane caught it in L2. Both guards now read each id through toRowId, the rule every other untrusted row id follows: an id it refuses resolves to nothing, so referencesOutsideTrip does not name it and unresolvedReferences does, and the answer is the same 400 on every engine. create() reads the payload's accommodation_id through toRowId as update() already did, instead of storing '0x5.0', which the reads' join could not cast back on Postgres. ReservationRow and ReservationTraveler move to reservation-rows.ts, the way reservation-inputs.ts holds the input shapes, so the service stays within its size baseline; the service exports them on and it is lowered to 1166.