Kyle Tse

Any plans to support loadingKey for mutation?

I found that prisma doesn't always add the limit to the query when using `cursor`. For example, `take: 5` should be `LIMIT 0, 5`. It seems there are some mechanism...

Any workaround solution? I want to store md5 of url by default for indexing. Something like: ``` url String @db.VarChar(2000) urlMd5 String @db.Char(32) @default(dbgenerated("md5(`url`)")) ```

It's even better if we can groupBy + _count + virtual field.

> Doesn't upsert solve this for you: https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#upsert > > Upsert basically will insert if `where` condition is not met, otherwise it will update the record which sounds like what...

Still waiting...

ok, I can migrate now after delete the rollback record in the last migration. It seems there is a checking issue on rollback record.

``` PS D:\project> prisma migrate dev Environment variables loaded from .env Prisma schema loaded from schema.prisma Datasource "db": MySQL database "project" at "127.0.0.1:3306" Database error code: 1062 Database error: Duplicate...

> @shtse8 it sounds a bit like you are using migrate's development commands in production. > > **In development** use `migrate dev` and `db push`. The development db is considered...

> I have a PR to change how we treat edited rolled back migrations in migrate dev — I am not convinced not resetting in this case is the right...