vs-cds-dbm

library0.0.4jsnpmunverified

Database deployment and migrations for SAP CAP models supporting non-HANA relational databases. Current stable version is 0.0.4. It extends @sap/cds with Liquibase-based CLI commands (deploy, load, diff, drop) and a custom build task for SAP BTP Cloud Foundry. Key differentiators: enables CAP on PostgreSQL via cds-pg adapter, automated delta deployments using zero-downtime schema cloning. Release cadence is low (single patch).

database

npm install vs-cds-dbm

github ↗package ↗

INSTALL

IMPORT

SIG · VS-CDS-DBM

vs-cds-dbm

databasejavascriptv0.0.4

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

cds-dbm

✓ npx cds-dbm deploy

✗ require('cds-dbm')

cds-dbm is a CLI tool; no JavaScript import. Use npx or add scripts in package.json.

cds-dbm/commands

✓ import { deploy } from 'cds-dbm/commands'

✗ import cdsDbm from 'cds-dbm'

Programmatic API is experimental; path must include /commands.

cds-dbm (package.json config)

✓ "cds": { "migrations": { "db": { ... } } }

✗ Missing migrations config block

Config must be in root package.json under cds.migrations.db. See README for required schema/clone/reference.

Installs cds-dbm, adds required migration config to package.json, runs deploy command.

npm install cds-dbm # In package.json, add: "cds": { "migrations": { "db": { "schema": { "default": "public", "clone": "_cdsdbm_clone", "reference": "_cdsdbm_ref" }, "deploy": { "tmpFile": "tmp/_autodeploy.json", "undeployFile": "db/undeploy.json" } } } } # Ensure JRE >= 8 is installed npx cds-dbm deploy

cds-dbm --version

Debug

Known issues

gotchaJRE >= 8 required on system; not bundled with npm

fix

Install Java 8+ and ensure java is on PATH

affects: >=0.0.0

breakingCDS configuration must be exactly as documented; schema names cannot be arbitrary

fix

Use exactly 'public' for default, '_cdsdbm_clone' for clone, '_cdsdbm_ref' for reference

affects: >=0.0.0

gotchacds-dbm only supports PostgreSQL via cds-pg; other databases not supported

fix

Ensure cds-pg (or compatible adapter) is installed and configured

affects: >=0.0.0

gotchaLiquibase is used internally; complex migrations may fail on unsupported DB features

fix

Test migrations on a development copy first; check Liquibase compatibility

affects: >=0.0.0

Errors

Common errors & fixes

Error: Cannot find module 'cds-dbm/commands'

Incorrect import path or not installed

fix

Run 'npm install cds-dbm' and use 'import { deploy } from 'cds-dbm/commands''

java.lang.RuntimeException: java.io.IOException: Cannot run program "java": error=2, No such file or directory

Java not installed or not in PATH

fix

Install JRE >= 8 and ensure 'java' command works in terminal

Error: cds-dbm requires a 'cds.migrations.db' configuration in package.json

Missing or incorrect configuration block

fix

Add the required migrations configuration as shown in the README

LiquibaseException: liquibase.exception.DatabaseException: Connection could not be created

Missing database credentials or driver

fix

Set environment variables for DB connection (e.g., DATABASE_URL) and install database adapter

Upgrade

Version history

0.0.4latest on npm

Audit

Dependencies

@sap/cdsrequiredRequired peer dependency for CAP models and service SDK

java-runtimeoptionalLiquibase requires JRE >= 8; must be installed on system

cds-pgoptionalPostgreSQL adapter for CDS (e.g., @cap-js/postgres or cds-pg)

Agent activity

27 hits · last 30 days

node