Hi folks, we've started building a project using prisma and have some questions on the workflow. Having worked for years with powerful ORMs like Django or Ruby on Rails, it feels weird to have my database, schema, and migration disconnected. We tried to setup our schema with Prisma migrate and the Prisma introspection, but with both approaches we keep running into bugs which slow us down a lot compared to other stacks. Writing migrations in db-migrate and then introspecting the database to get a Prisma schema feels odd, as there is no single place for a model anymore where I could also store meta data like field names, field labels, etc. Field descriptions could certainly be added on the GraphQL layer, but then again, I'm creating another place with "model information". Are we missing something here? How do you manage this or which ORM are you using? Or is prisma just not there yet? Prisma migrate seems to go into the right direction but is still experimental. From using it now for a few weeks now there seem to be a lot of things missing that e.g., Django's ORM does for you out of the box. I tried to find more information when prisma migrate is supposed to move out of the experimental status, but couldn't find anything. Maybe, somebody can shed some light on my questions here. Thanks already for any answers.

Can you elaborate in the things that are missing in

migrate

? What Django features are you referring to?