-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[EPIC] Re-Introspection #2829
Copy link
Copy link
Closed
prisma/prisma-engines
#1061Labels
kind/featureA request for a new feature.A request for a new feature.tech/enginesIssue for tech Engines.Issue for tech Engines.tech/engines/introspection engineIssue in the Introspection EngineIssue in the Introspection Enginetopic: previewFeaturesIssue touches on an preview feature flagIssue touches on an preview feature flagtopic: re-introspection
Milestone
Metadata
Metadata
Assignees
Labels
kind/featureA request for a new feature.A request for a new feature.tech/enginesIssue for tech Engines.Issue for tech Engines.tech/engines/introspection engineIssue in the Introspection EngineIssue in the Introspection Enginetopic: previewFeaturesIssue touches on an preview feature flagIssue touches on an preview feature flagtopic: 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:
@mapand@@mapcuid()anduuid()) #2534: Keep defaults that are not persisted in the database@updatedAt#3335: Keep@updatedAtWe might also decide that some of them are not worth the effort.
Some more issues are listed related to this under: topic: re-introspection