Seeing that introspection is the recommended migration strategy, will prisma introspect be a first-class citizen once migrate is stable? I see things such as

@map

directives being lost from introspect, so does it mean that to support those things we will have to move from existing migration solution (eg. knex or umzug) to prisma migrate?

Interesting question, @jknr! I’m with the product team at Prisma, currently focusing on database migrations. I anticipate once we have a production-ready solution for DB migrations, introspection will be less in the spotlight but continue being supported. How much we continue investing in making introspection great will ultimately depend on how much value it brings to our users. If introspection is mission critical for our users, it’s likely we invest even more in making introspection top of the lime. I’d love to hear more about how you are using today and would use it in the future. In addition, I am also seeking feedback on a prototype for database migrations that is different from prisma migrate today and would love your input. I will DM to see if you are willing and have some some time to jump on a call! 😉

Or to be concrete: https://github.com/prisma/prisma/releases/tag/2.1.0, headline "Re-Introspection" With the command

npx prisma introspect --experimental-reintrospection

all your manual changes should be kept around. We will soon merge this experimental command into the main

introspect

to make this the default behavior.

I should really start to pay closer attention to release notes! This is great!