Schema evolution
Getting a model change into a database that already holds data, in every tenant, without losing any of it. Generating the initial schema and migrating one that already holds data are often treated as the same step.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
Overview
Runs cds deploy, deriving and applying the delta for the model changes a compiler can work out on its own.
Brings an HDI container up to the current design-time files as a delta: added and modified files are deployed, deleted ones only when undeploy.json or --auto-undeploy asks for it. For SAP HANA it is what cds deploy runs.
A Node.js coverage assessment has not been written. View all flavors
Migration Check: flags incompatible CDS model changes and maintains a whitelist of compatible ones via the cdsmc CLI.
A Node.js coverage assessment has not been written. View all flavors
Artifacts
Details
Coverage
For your agent
- Ref
capability:schema-evolution- JSON
- /capabilities/schema-evolution.json
- MCP
- Connecting an agent