CapabilityData & PersistenceNode.js, read from its artifacts

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

SAP SHIPS
@sap/cds

Runs cds deploy, deriving and applying the delta for the model changes a compiler can work out on its own.

SourceSchema Evolutionchecked
@sap/hdi-deploy

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

THE COMMUNITY ADDS
@cap-js-community/common

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

Artifacts6

6 of 6 artifacts
ArtifactSignals
Build tools1
cds-dbmDelta deployment and migrations for CAP database adapters
Signals
Archived+1
CLI tools1
@quadrio/cds-dbmFork of cds-dbm with deploy, load, diff and drop tasks
Signals
Quiet
Packages4
@cap-js-community/commonSix CAP features in one package, from replication cache to rate limits
Signals
Functional boundary
@sap/cdsCAP Node.js runtime
Signals
none
@sap/cds-mtxsMultitenancy, tenant provisioning and extensibility for CAP
Signals
none
@sap/hdi-deployNode.js deployer for SAP HANA Deployment Infrastructure containers
Signals
none

Details

Coverage
statecore and community, CAP, Node.js, derived
For your agent
Ref
capability:schema-evolution
JSON
/capabilities/schema-evolution.json
MCP
Connecting an agent