From b4759e991be28fe8f5dfe7e84099e3d24898884c Mon Sep 17 00:00:00 2001 From: Trezy Date: Wed, 27 May 2026 14:49:46 -0500 Subject: [PATCH] fix: restore `granted_at` default in migrations Signed-off-by: Trezy Signed-off-by: Trezy --- .../postgres/20260501000000_scripts_by_trigger.sql | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/migrations/postgres/20260501000000_scripts_by_trigger.sql b/migrations/postgres/20260501000000_scripts_by_trigger.sql index a277839..a7d3bee 100644 --- a/migrations/postgres/20260501000000_scripts_by_trigger.sql +++ b/migrations/postgres/20260501000000_scripts_by_trigger.sql @@ -45,14 +45,15 @@ CREATE INDEX idx_dead_letter_scripts_resolved_at ON dead_letter_scripts (resolved_at); -- Permissions: management for users who can manage lexicons; read for those who can read. -INSERT INTO user_permissions (user_id, permission) -SELECT user_id, 'scripts:manage' +-- granted_at lost its DEFAULT in 20260318 (type change to TEXT), so we must supply it. +INSERT INTO user_permissions (user_id, permission, granted_at) +SELECT user_id, 'scripts:manage', granted_at FROM user_permissions WHERE permission = 'lexicons:create' ON CONFLICT (user_id, permission) DO NOTHING; -INSERT INTO user_permissions (user_id, permission) -SELECT user_id, 'scripts:read' +INSERT INTO user_permissions (user_id, permission, granted_at) +SELECT user_id, 'scripts:read', granted_at FROM user_permissions WHERE permission = 'lexicons:read' ON CONFLICT (user_id, permission) DO NOTHING; -- 2.51.2