was so excited about Prisma, seems the SDL to database schema migration/create has one huge flaw in my mind, every relationship needs its own table, some entities will have several relationships generating a large amount of tables and joins to complete simple queries. The one very concerning design decision I've seen so far, what the heck is the problem with FKs ?!?

I think it will be easier to respond if you construct a minimal example where you show what prisma generates and what you’d want to happen instead :)

Hey @Ben, Prisma operates in two modes; - either Prisma fully dictates your DB schema, this is the default mode - or you use introspection to read the DB schema In both cases the generated GraphQL API is the same. You can use introspection today for Postgres databases. This way you fully control FKs, data types etc. You can read more here: https://www.prisma.io/docs/reference/service-configuration/data-model/introspection-aeb6diethe We are working on an introspection feature for MySQL as well: https://github.com/prismagraphql/prisma/issues/2506