Jan Piotrowski

What is the explanation behind this? > If it is not removed, the migration will fail with the following error message: > `The underlying table for model `_prisma_migrations` does not...

Doesn't that imply a potential bug in our logic reading `_prisma_migrations`, that we should specify the schema explicitly instead of relying on the search paths? (That would still work, correct?)...

~https://github.com/prisma/prisma/issues/7960 is closed - so this is considered done. If that is not the case, please open a new issue and describe exactly what is missing and what the use...

Thanks for the report. Let's see if someone else has the same problem with Chrome(ium) 100.

(Might also just be a Prisma Client problem) Update: Now an issue at https://github.com/prisma/prisma/issues/12608

@sreuter I would love to, but I don't work at Prisma any more and so unfortunately can not help with this problem. (In the past https://github.com/prisma/ecosystem-tests/tree/dev/community-generators/prisma-json-schema-generator would have been used...

> (I couldn't find a generic develop branch or anything of the sort) @Jackman3005 Each merge to `main` in `prisma/prisma` is shipped to npm as a `-dev.x` version on the...

> For databases that support naming primary key constraints (Postgres, SQLServer), we can check if the table is being renamed by looking at the key. If the key is the...

Heads up: We had an internal conversation that we probably would want to offer this to our users as a choice, via an interactive prompt, instead of using some heuristics...

This is not really a feature we want our users to actually use and play around with, as it concerns an area that our users should optimally never have to...