Matt Mueller

Moving this to Post-Beta. Absolutely great to have, but not essential for MVP.

> The 3rd layer is missing in this specification in my opinion. Omitting this information leads to an incomplete schema. Here's an example Good call, strongly agree. In fact, I...

updated the spec based on feedback and added an illustration. the terminology is a first-draft and we're not sure what / where / if things like `@go("decimal.Decimal")` should be possible....

Thanks for reviewing @divyenduz! I've updated the `Reduce duplication with more attributes` to offer up one solution for `count(id)`. Let me know if that still doesn't make sense.

While looking into views, stored procedures and functions, it's become obvious that the Prisma schema may get bloated with complex views, particularly from introspection. To keep our schema clean going...

Regarding views in a separate file:

@mavilein this proposal currently assumes we'd be able to treat these SQL view files declaratively using something like `create or replace view`. A snapshot of these files could also live...

Another option is following suit with terraform and having a `file(filename)` function. Something like: ```sql view BrazilCustomers { name String email String count Int @@file("./myview.sql") } ```

Sounds good for Typescript – I guess for the others like Go, it can be a runtime error.

Thanks for the feedback! I'll answer these questions here then persist it in the PR when everything is resolved. **Do I need to provide both cursor and take? If no,...