mAi
6401a8198d
m's ask 2026-05-20 09:42. Eighth HLC office alongside Munich, Düsseldorf, Hamburg, Amsterdam, London, Paris, Milan. - `internal/offices/offices.go` — append Madrid to All[] (display order: end of list, after Milan). Doc comment refreshed to point at the actual current CHECK constraints (users mig 002 + partner_units mig 018/024/027), not the obsolete akten reference from before projects-v2. - `internal/offices/offices_test.go` — add `madrid` to the valid-keys table. - mig 106 — extend the two CHECK constraints on users.office and partner_units.office. Idempotent (DROP IF EXISTS), audit_reason set_config at top, dry-run validated against the live youpc paliad schema (BEGIN; ALTER...; ROLLBACK). Frontend picks up Madrid automatically via GET /api/offices. Admin UI for managing firm office list is a separate longer-term issue — m's "for now, just add Madrid already" path.
29 lines
962 B
SQL
29 lines
962 B
SQL
-- Revert mig 106 — drop 'madrid' from the office CHECK constraints.
|
|
--
|
|
-- Will fail if any users.office or partner_units.office row carries
|
|
-- 'madrid' — that's intentional (the down has no opinion on the data;
|
|
-- caller must clean up first or accept the failure).
|
|
|
|
SELECT set_config(
|
|
'paliad.audit_reason',
|
|
'mig 106 down: restore pre-madrid office CHECK on users + partner_units',
|
|
true);
|
|
|
|
ALTER TABLE paliad.users
|
|
DROP CONSTRAINT IF EXISTS users_office_check;
|
|
ALTER TABLE paliad.users
|
|
ADD CONSTRAINT users_office_check
|
|
CHECK (office IN (
|
|
'munich', 'duesseldorf', 'hamburg',
|
|
'amsterdam', 'london', 'paris', 'milan'
|
|
));
|
|
|
|
ALTER TABLE paliad.partner_units
|
|
DROP CONSTRAINT IF EXISTS partner_units_office_check;
|
|
ALTER TABLE paliad.partner_units
|
|
ADD CONSTRAINT partner_units_office_check
|
|
CHECK (office IN (
|
|
'munich', 'duesseldorf', 'hamburg',
|
|
'amsterdam', 'london', 'paris', 'milan'
|
|
));
|