Help us improve the Prisma CLI 馃殌 #26381
Replies: 8 comments 1 reply
|
Make
running interactively could instead connect to db via admin connection, display status of recent migrations, provide for selection of migrations by arrow keys and spacebar to select etc to flag as rolled back or successful. |
|
native support for different environments e.g. dev / canary / staging / production - for different database admin connection URLs etc currently have to do various gymnastics with env vars / dotenv files per environment before running prisma CLI commands (migrate, studio) - using mess of unruly package.json scripts as shorthand much nicer to be able to do e.g. would then unlock adding per-environment restrictions/safeguards e.g. disallow |
|
A full database reset seems to happen any time data needs deletion, even in cases where the deletion will not affect other tables. It would be great to minimize resets. Before continuing, the CLI would warn you when a full database reset was required and why |
|
Allow Prisma to use Bun. My application runs on Bun, but I must have Node installed if I want to use the CLI. |
|
I think better revert command |
|
when i use npx prisma migrate dev --name xx --create-only i can't rollback/delete this migration if i don't need before dev/deploy. |
|
rds proxy full support |
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone 馃憢
We鈥檙e exploring ways to improve the Prisma CLI and would love your input! Whether you're a daily user or just getting started, your feedback can help us make the CLI experience even better.
Some questions to get you thinking:
Drop your thoughts below! Your insights will directly shape the future of the Prisma CLI 馃挌
All reactions