Prisma

Hi, does anyone know if it's possible to prefer a "soft reset" (don't nuke the db /schema) over a "hard reset" when calling `prisma migrate reset` ? I'm finding that the hard reset is screwing with the various permissions I have set up (the credentials I give to my application can no longer access the schema as it's been destroyed / recreated) and I'd much prefer a `--prefer-soft-reset` cli option over creating a third set of credentials for the sole purpose calling reset such that they can read/write tables but not destroy the schema and thus triggering a "soft reset".

Hey Joshua :wave: I’ve reached out to the Migrate team ands asked them if they an idea about this :slightly_smiling_face:

So, it seems like this is currently not possible unfortunately, but we do have an open feature request for it here already: <https://github.com/prisma/prisma/issues/5596> It would be great if you could leave a :thumbsup: and ideally a comment on the issue, this helps our Product and Engineering teams prioritize it on the roadmap!

By the way, if you want a reset without database deletion, `db push` with an empty schema should work :slightly_smiling_face: