The database moved to a container of our own; the platform is gone. This takes out what was left of it — and, where the leftovers were load bearing, moves rather than deletes. Moved, not deleted: supabase/migrations/ -> db/migrations/ the schema's source of truth supabase/build-org.ts -> scripts/build-org.ts lib/supabase/types.ts -> lib/types.ts 52 import sites repointed The bookkeeping needed care. It lived in `supabase_migrations.schema_migrations`, and simply renaming the schema would have left the runner facing an empty table: it would have called all 67 migrations pending and replayed them against a database that is long since current. So the runner now creates `migrationen.schema_migrations` and, once, copies the old rows across — guarded so a second run does nothing and a fresh database skips it entirely. Only then does migration 20260907100000 drop the old schema. Deleted: the CLI config, the seed, the historical schema/function dumps (nothing read them), scripts/umzug-von-supabase.sh (the move is done), and both Supabase packages plus the CLI. Nothing in the application imported them — the build now succeeds with no environment variables at all, which is the proof. Integration tests: six of them signed in through Supabase Auth and asserted against the anon key and the service role. That model is gone, so the tests were not portable — they are deleted. session-context and employee-status-filter already ran on pg and are untouched; om-reporting is ported to a direct connection because it guards a real risk (the reporting line rule exists twice, once in SQL and once in TypeScript). CI: the integration job started a Supabase stack. It now runs a postgres service, applies deploy/db-init and every migration to an empty database — that was the valuable part, and it still holds — then checks that a second run is a no-op, which is what proves the bookkeeping works. Docs: security-review.md audited a service-role key, a cookie adapter and auth.users, none of which exist. Restating findings about removed components would suggest today's system had been reviewed; it has not. It now records what was removed and says a fresh review is due. data-model.md was already marked obsolete and described the pre-OM schema; azure-migration.md was a plan for a route not taken. Both deleted. Verified: npm ci, typecheck, lint, 445 tests, build — all clean without the packages. Integration tests skip cleanly with no database. Migration SQL and the runner are reviewed but NOT executed: no Docker here, and the old instance no longer resolves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
79 lines
3.4 KiB
PL/PgSQL
79 lines
3.4 KiB
PL/PgSQL
-- "Angehörige" — dependents/family members tracked per employee (spouse,
|
|
-- children, ...), relevant for payroll/insurance. One employee can have
|
|
-- several. Editing is add/remove only — fix a mistaken entry by deleting
|
|
-- and re-adding it, same as "Position löschen" — no in-place edit RPC.
|
|
|
|
create table employee_dependents (
|
|
id uuid primary key default gen_random_uuid(),
|
|
employee_id uuid not null references employees(id) on delete cascade,
|
|
first_name text not null,
|
|
last_name text not null,
|
|
relationship text not null check (relationship in ('Ehepartner:in', 'Lebenspartner:in', 'Kind', 'Sonstige')),
|
|
sv_nummer text,
|
|
birth_date date not null,
|
|
created_at timestamptz not null default now()
|
|
);
|
|
create index on employee_dependents (employee_id);
|
|
|
|
-- RLS only narrows what an already-GRANTed role may do; the "grant all ...
|
|
-- to anon, authenticated, service_role" default privilege (see
|
|
-- 20260714120500_default_grants.sql) already covers this new table.
|
|
alter table employee_dependents enable row level security;
|
|
create policy "employee_dependents_hr_all" on employee_dependents for all
|
|
using (is_hr_user()) with check (is_hr_user());
|
|
|
|
-- ── Angehörige:n hinzufügen ───────────────────────────────────────────
|
|
create or replace function add_employee_dependent(payload jsonb)
|
|
returns uuid language plpgsql as $$
|
|
declare
|
|
v_id uuid;
|
|
v_employee_id uuid := (payload->>'employee_id')::uuid;
|
|
v_employee_name text;
|
|
begin
|
|
perform require_hr_admin();
|
|
select first_name || ' ' || last_name into v_employee_name from employees where id = v_employee_id;
|
|
if not found then
|
|
raise exception 'Mitarbeiter:in nicht gefunden.';
|
|
end if;
|
|
|
|
insert into employee_dependents (employee_id, first_name, last_name, relationship, sv_nummer, birth_date)
|
|
values (
|
|
v_employee_id, payload->>'first_name', payload->>'last_name', payload->>'relationship',
|
|
nullif(payload->>'sv_nummer', ''), (payload->>'birth_date')::date
|
|
)
|
|
returning id into v_id;
|
|
|
|
insert into audit_log (actor_user_id, actor_name, action, target_label, target_employee_id, details)
|
|
values (
|
|
auth.uid(), current_actor_name(), 'Angehörige:r hinzugefügt', v_employee_name, v_employee_id,
|
|
(payload->>'first_name') || ' ' || (payload->>'last_name') || ' (' || (payload->>'relationship') || ')'
|
|
);
|
|
|
|
return v_id;
|
|
end;
|
|
$$;
|
|
|
|
-- ── Angehörige:n entfernen ────────────────────────────────────────────
|
|
create or replace function delete_employee_dependent(payload jsonb)
|
|
returns void language plpgsql as $$
|
|
declare
|
|
v_dep employee_dependents%rowtype;
|
|
v_employee_name text;
|
|
begin
|
|
perform require_hr_admin();
|
|
select * into v_dep from employee_dependents where id = (payload->>'dependent_id')::uuid;
|
|
if not found then
|
|
raise exception 'Angehörige:r nicht gefunden.';
|
|
end if;
|
|
select first_name || ' ' || last_name into v_employee_name from employees where id = v_dep.employee_id;
|
|
|
|
delete from employee_dependents where id = v_dep.id;
|
|
|
|
insert into audit_log (actor_user_id, actor_name, action, target_label, target_employee_id, details)
|
|
values (
|
|
auth.uid(), current_actor_name(), 'Angehörige:r entfernt', v_employee_name, v_dep.employee_id,
|
|
v_dep.first_name || ' ' || v_dep.last_name || ' (' || v_dep.relationship || ')'
|
|
);
|
|
end;
|
|
$$;
|