Nikolas

Hey @medz 👋 thank you so much for opening this issue, as well as for your work on the Dart version of Prisma Client and the `query-engine-c-api` repo! All of...

Just coming here to share a workaround by one of our community members who recently ran into this issue and shared their [workaround in the public Prisma Slack](https://prisma.slack.com/archives/CCWDULGUW/p1663644045180299): > I...

Removed from docs for now, thanks for the heads-up @nlarusstone 🙏

> however, other dependencies (i.e. nestjs) uses @prisma/client to import, so the new location is ignored. @kokokenada Do you think this could be configurable in your NestJS app? If no,...

@respectTheCode Sorry for the confusion! We're indeed still working on the Rust rewrite (and are making great progress). The bullet on the roadmap was a bit redundant with the point...

Hey everyone 👋 🚨 This is a **final reminder** that you have **3 weeks close your Prisma 1 Cloud account** before it gets **sunset on September 1st, 2022**. 🚨 If...

There is no example for a `count` aggregation, I'm guessing it looks like this: ```graphql { postsConnection { aggregate { count } } } ``` Please confirm or correct!

@beeplin Just a heads-up that I've edited your comment and changed `datamodel v2` into `v1.1` since that's how we call this iteration of the datamodel now.

Commenting so this issue won't be considered stale 🙏

@janpio We do have docs that state that `default(now())` is DB-level but `@updatedAt` is Prisma-level. Do you think we need more information than that? If so, what specficically?