Joël Galeran

After a short investigation I found out that it was fixed in our internal dev version `4.3.0-dev.37` The prisma-engines PR is about the new preview feature [`filteredRelationCount`](https://www.prisma.io/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#filter-the-relation-count) from @Weakky https://github.com/prisma/prisma-engines/pull/3057...

I can reproduce: (see `Executed in 31.60 secs`) ``` time npx prisma db push Environment variables loaded from prisma/.env Prisma schema loaded from prisma/schema.prisma Datasource "db" Error: MongoDB error Server...

@tomhoule I also get something close to 30s when doing `time ts-node main.ts` with a Prisma Client query. Same behavior.

Can reproduce in our internal dev version `4.4.0-dev.30` For Client here is the script ```ts import { PrismaClient } from '@prisma/client' async function main() { const prisma = new PrismaClient()...

Note: Looks related to an issue with the Decimal native type

@agz-jrugel Could you give us an example value that you have in your database that caused this crash?

Related issues so far https://github.com/prisma/prisma/issues/9786 https://github.com/prisma/prisma/issues/10265

Thank you @AndrewSouthpaw for your detailed feedback 👍🏼

Tested with `4.3.0-dev.27` | Command | Success | Error | Notes | | --- | --- | --- | --- | | `format` | 0 | 1 (e.g. schema validation...

Here is - the issue about `migrate status` https://github.com/prisma/prisma/issues/14860 - the issue about `studio` https://github.com/prisma/prisma/issues/14861 - the issue about `migrate dev` https://github.com/prisma/prisma/issues/14862