CodeCow/stack
1
0
Fork 0
mirror of https://github.com/stack-auth/stack.git synced 2026-06-04 21:04:37 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Add schema to migration that was missing it

Browse Source
This commit is contained in:
Konstantin Wohlwend 2026-05-19 16:14:28 -07:00
parent fcbb2492c4
commit 0848a1aaed
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.cursor/commands/pre-push.md
View File

@ -1 +1 @@
Please compare `origin/dev` to `origin/main` (feel free to check out the dev branch if needed) and ensure that all migrations are backwards compatible. In what ways could breakage occur? Report the result to me in detail. Anything else that's scary that could occur, or that we should think about while migrating?
Please compare `origin/dev` to `origin/main` (feel free to check out the dev branch if needed) and ensure that all migrations are backwards compatible. In what ways (DB, API, or otherwise) could breakage occur? Report the result to me in detail. Anything else that's scary that could occur, or that we should think about while migrating? Should we migrate first and upgrade the code second, or the other way around? Are rollbacks safe? Think hard.

2
apps/backend/prisma/migrations/20260507000000_add_project_user_last_active_at_idx/migration.sql
View File

@ -2,4 +2,4 @@
-- SINGLE_STATEMENT_SENTINEL
-- RUN_OUTSIDE_TRANSACTION_SENTINEL
CREATE INDEX CONCURRENTLY IF NOT EXISTS "ProjectUser_lastActiveAt"
ON "ProjectUser"("tenancyId", "isAnonymous", "lastActiveAt");
ON /* SCHEMA_NAME_SENTINEL */."ProjectUser"("tenancyId", "isAnonymous", "lastActiveAt");