Maurice
ba28b5538d
test(server): keep the legacy TEXT shape of a booking's stay link
...
reservations.accommodation_id is TEXT, and every writer stores a stay id
in the shape the legacy statement bound it (`14.0`, see
legacyBoundIntegerText). The converted specs wrote and matched the bare
`14` instead, so a lookup of a booking the service had linked would miss
it and a seeded link would not look like one the app writes. They now go
through legacyBoundIntegerText, the same helper the services use.
2026-10-08 18:45:57 +02:00
..
2026-10-08 18:45:20 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:43:06 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:44:39 +02:00
2026-10-08 18:45:20 +02:00
2026-10-08 18:41:01 +02:00
2026-10-06 19:27:30 +02:00
2026-06-16 22:22:45 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 22:43:09 +02:00
2026-10-08 18:45:20 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-08-15 22:48:16 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:42:10 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:44:00 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:41:01 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:45:20 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:45:57 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:45:20 +02:00
2026-10-08 18:44:00 +02:00
2026-10-08 18:44:08 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-09-26 10:36:02 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:44:39 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 22:43:09 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-08 18:45:20 +02:00
2026-10-08 18:45:20 +02:00
2026-10-06 19:27:30 +02:00
2026-10-06 19:27:30 +02:00