fix: auto-migrate after DB restore and force re-login

- After importing a backup, run prisma migrate deploy so any schema
  migrations the backup is missing are applied automatically. This
  prevents pages from failing due to missing tables/columns when the
  backup was taken on an older version of the app.
- Force logout and redirect to login after a successful restore so the
  JWT is refreshed against the restored database (prevents userId
  mismatch causing user-scoped queries to return empty results).
- Fix getTotalPatientCount() in /status route to pass userId so it
  counts only the current user's patients instead of all patients.
- Add prisma.$connect() after $disconnect() to ensure a clean reconnect.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
ff
2026-05-17 22:31:12 -04:00
parent b9e888fc7f
commit 5508a90d28
231 changed files with 1629 additions and 14854 deletions

View File

@@ -1,7 +1,8 @@
import * as z from 'zod';
import { Prisma } from '../../generated/prisma';
import Decimal from 'decimal.js';
import type { Prisma } from '../../generated/prisma';
import Decimal from "decimal.js";
// DECIMAL HELPERS
//------------------------------------------------------
@@ -23,7 +24,7 @@ export const isValidDecimalInput = (
if (v === undefined || v === null) return false;
return (
// Explicit instance checks first
v instanceof Prisma.Decimal ||
v instanceof Decimal ||
// If Decimal.js is present and imported by the generator, this symbol exists at runtime
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore - Decimal may be undefined when not installed; codegen controls the import