litellm/litellm-proxy-extras/litellm_proxy_extras
ryan-crabbe-berri 90ba89e1cc fix(migration): add user FK as NOT VALID so no existing rows are touched
Self-hosted databases can contain keys whose user_id references a user
deleted before the constraint existed, or used as free-form attribution.
Nulling those rows was irreversible data mutation and the validating
ALTER TABLE could fail a deploy. NOT VALID adds the constraint without
reading a single existing row, enforcing only new writes; a best-effort
VALIDATE then upgrades it to fully valid on clean databases and quietly
leaves it NOT VALID where orphans exist. The migration can no longer
fail or modify data under any database state
2026-07-27 12:37:25 -07:00
..
migrations fix(migration): add user FK as NOT VALID so no existing rows are touched 2026-07-27 12:37:25 -07:00
__init__.py install prisma migration files - connects litellm proxy to litellm's prisma migration files (#9637) 2025-03-29 15:27:09 -07:00
_logging.py style: run black formatter on files from main merge 2026-04-17 13:02:59 -07:00
schema.prisma chore: sync schema.prisma copies from root 2026-07-27 18:29:19 +00:00
utils.py [Fix] v2 resolver: swallow non-connection DB errors; wrap resolve failures 2026-04-21 15:53:07 -07:00