[EPIC] Re-Introspection

We want to remove one of the remaining big pain points of Introspection: If you manually adjusted your data model after introspection (to rename fields or models, or add default IDs for example) these changes are currently lost once you introspect again (“re-introspect”, for example, because your database was changed manually or migrated by another tool).

This project consists of many individual problems that we are tackling one by one:

• https://github.com/prisma/prisma/issues/2503: Keep manual changes to relation field names
• https://github.com/prisma/prisma/issues/2545: Keep @map and @@map
• https://github.com/prisma/prisma/issues/2534: Keep defaults that are not persisted in the database
• https://github.com/prisma/prisma/issues/1997: Keep order of models of existing Prisma schema
• https://github.com/prisma/prisma/issues/2968: Keep order of fields of existing Prisma schema
• https://github.com/prisma/prisma/issues/3052: Keep comments in schema
• https://github.com/prisma/prisma/issues/3335: Keep @updatedAt

We might also decide that some of them are not worth the effort.

Some more issues are listed related to this under: https://github.com/prisma/prisma/labels/topic%3A re-introspection

[kennytraction]

Thanks for putting the effort into this feature. It is greatly appreciated!

We have only had a few issues with re-introspection:

• Renamed relations which is fixed and working in v2.1.1
• @updatedAt is not maintained. https://github.com/prisma/prisma/issues/2075
• Error with renamed relations to the same table. I have created an issue and explained it here: https://github.com/prisma/prisma/issues/2844

[janpio]

I tested prisma introspect --experimental-reintrospection on the database @nikolasburk posted in another issue, where he used @@map and renamed relation fields: https://github.com/prisma/prisma/issues/2425#issuecomment-649709485 All changes were kept 🚀