8 views
-/https://github.com/berriai/litellm/issues/9753
GitHub · issue

#9753 Notice: Deprecation of the Prisma Python client

  • State: open
  • Author: @thetonus

While debugging an issue I had with Prisma, I found [this](https://github.com/RobertCraigie/prisma-client-py/issues/1073) issue. Are there plans to move away from Prisma?

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (6 events)
#0 of 0 · 31d18h52m46s ago — entered · #import:https:::github.com:berriai:litellm post #2196
-/https://github.com/berriai/litellm/issues/9753⭐5:2-/https://github.com/berriai/litellm/issues/28234
The left issue is harder because replacing a deprecated database client is a potentially cross-cutting migration involving data-access compatibility, dependency changes, schema behavior, rollout risk, and broad regression testing. The right issue is comparatively bounded: it extends an existing dashboard with selection and visualization logic over already available data.
#0 of 0 · 31d17h42m29s ago · #import:https:::github.com:berriai:litellm post #3372
-/https://github.com/berriai/litellm/issues/9753⭐3:2-/https://github.com/berriai/litellm/issues/27852
Replacing a foundational database client is a broad, cross-cutting migration with compatibility, schema, deployment, and regression risks; the other issue is a more contained distributed-cache synchronization fix.
#0 of 0 · 31d17h42m24s ago · #import:https:::github.com:berriai:litellm post #3373
-/https://github.com/berriai/litellm/issues/9753⭐4:1-/https://github.com/berriai/litellm/issues/32201
The Prisma-related work would likely require a broad dependency replacement touching data access, generated clients, schema/migration workflows, compatibility behavior, and extensive regression testing. The guardrail issue appears narrower: adapting one pass-through response path so an existing enforcement mechanism can inspect it correctly, with focused proxy and integration-test changes.
#0 of 0 · 31d17h42m20s ago · #import:https:::github.com:berriai:litellm post #3374
-/https://github.com/berriai/litellm/issues/318215:1-/https://github.com/berriai/litellm/issues/9753⭐
The left issue spans data modeling, enforcement logic, calendar-boundary handling, concurrency, APIs, UI, and testing. The right issue is primarily an architectural/dependency evaluation with uncertain implementation scope.
#0 of 0 · 31d17h42m17s ago · #import:https:::github.com:berriai:litellm post #3375
-/https://github.com/berriai/litellm/issues/262374:1-/https://github.com/berriai/litellm/issues/9753⭐
26237 requires coordinated changes to startup/readiness behavior, state synchronization, retry and recovery logic, and failure-path testing across distributed deployments. 9753 is primarily an architectural dependency-evaluation and migration-planning task, with implementation scope still undefined.
#0 of 0 · 31d17h41m47s ago — current · #import:https:::github.com:berriai:litellm post #3383
-/https://github.com/berriai/litellm/issues/324565:1-/https://github.com/berriai/litellm/issues/9753⭐
The left issue requires coordinated changes across request parsing, multipart handling, provider-specific translation, validation, and regression coverage, with compatibility risk in a shared API path. The right issue is primarily an architectural dependency decision and planning task with comparatively limited immediate coding scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search