PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
@cap-js/db-service
The base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQLPostgreSQLoutside the atlasA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL. and HANA specialise rather than reimplement.
Database connectorsCAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).
Part of
@cap-js/cds-dbs@cap-js/cds-dbsartifactThe monorepo behind CAP's SQL database services — the base service, SQLite, PostgreSQL and HANA all live here, which is why they version together.
@sap/cds^10@sap/cdsartifactThe peer range, as published.
Who is behind it
SAP Cloud Application Programming ModelSAP Cloud Application Programming ModelOrganisationMaintains this In the atlas: maintains 34@cap-jsmaintainerJohannes VogtPersonContributes to this In the atlas: maintains 1, contributes to 28, wrote 10@AkatuoroArley Triana MorinPersonContributes to this In the atlas: contributes to 9, wrote 1@arleytmAndreas SchmidtPersonContributes to this In the atlas: contributes to 6@aschmidt93Bob den OsPersonContributes to this In the atlas: contributes to 13@BobdenOsAndre MeyeringPersonContributes to this In the atlas: contributes to 10@bugwelleCAP BotPersonContributes to this In the atlas: contributes to 5@cap-botsChristian GeorgiPersonContributes to this In the atlas: maintains 1, contributes to 53@chgeoChristian SchüringsPersonContributes to this In the atlas: contributes to 25@cschueringsDaniel HutzelPersonContributes to this In the atlas: contributes to 32, wrote 3@danjoaDaniel O'GradyPersonContributes to this In the atlas: contributes to 10@daogrady35 contributors
Before choosing this
crawled
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1from Database connectorsA covered CAP application uses a connector to copy or persist SAP product data in a non-SAP database product.
§ 1License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
The connector itself does not decide the licence boundary. Section 1 makes the destination and purpose of extraction relevant, including the scoped exception for interoperability with an SAP product.
declared, Where the library runs once installed: inside its host (loaded into the CAP application, installed into the ABAP system, loaded by the UI5 application), in a program of your own, or only at build time.
Distributed through
does not say
declared, How it is installed, as its documentation tells a user to get it.
Connections2
Group by
NodeRelationConditionBasis
Functional1
Database connectorsDatabase connectorscapabilityConnecting a data model and its queries to a databaseSAP and community, narrow by design
→provides
none
authored
provides Database connectors
Functional, authored
Connecting a data model and its queries to a database
Lineage1
@cap-js/cds-dbs@cap-js/cds-dbspackageMonorepo of CAP's SQL database servicessap official, cap
→part of
none
stated
part of @cap-js/cds-dbs
Lineage, stated
Basis
“It contains subfolders for the [base database service implementation](./db-service/) as well as the implementation of this interface for [SQLite](./sqlite/), [PostgreSQL](./postgres/) and [SAP HANA](./hana/).”cap-js/cds-dbs — README, checked “Each of the subfolders is published as individual npm module.”cap-js/cds-dbs — README, checked
Welcome to the base database service for SAP Cloud Application Programming Model Node.js. This service forms the core of all supported databases and is the base of our streamlined database architecture.
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues.
Contribution
Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Licensing
Copyright 2024 SAP SE or an SAP affiliate company and cds-dbs contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
Database connectorsDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to schema evolution.SAP and community, narrow by design
SAP HANA CloudSAP HANA CloudserviceThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btpManaged SAP HANA database service on BTP
PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionserviceA managed PostgreSQL from the underlying hyperscaler — AWS, Azure, Google Cloud or Alicloud — consumed through a BTP service binding.sap official, btpManaged PostgreSQL from the hyperscaler via a BTP service binding
com.sap.cds:cds-feature-hanacom.sap.cds:cds-feature-hanapackageThe CAP Java feature that wires a Maven application to SAP HANA Cloud, the production default among CAP's supported databases.sap official, capSAP HANA Cloud datasource for CAP Java applications
com.sap.cds:cds-feature-jdbccom.sap.cds:cds-feature-jdbcpackageConnects the CAP Java runtime to JDBC databases through the CDS4j JDBC runtime: H2 and SQLite, which capire names for local development and CI tests rather than enterprise use.sap official, capJDBC runtime for H2 and SQLite in CAP Java
com.sap.cds:cds-feature-postgresqlcom.sap.cds:cds-feature-postgresqlpackageThe CAP Java feature that wires a Maven application to PostgreSQL as its datasource beside SAP HANA, with limitations capire lists: schema evolution first, and no multitenancy or extensibility yet.sap official, capPostgreSQL datasource for CAP Java applications
com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bompackageThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versions
@cap-js/hana@cap-js/hanacds-pluginThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, capSAP HANA database service for CAP
@cap-js/postgres@cap-js/postgrescds-pluginThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, capPostgreSQL database service for CAP
@cap-js/sqlite@cap-js/sqlitecds-pluginThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, capSQLite database service for CAP, in memory during development
cap-postgres-btp-connectivitycap-postgres-btp-connectivitycds-pluginConnects a CAP Node.js application to a PostgreSQL database that is not publicly reachable, tunnelling through BTP Connectivity and the Cloud Connector.independent, capTunnels CAP Node.js to a private PostgreSQL via Cloud Connector
cds-mongodbcds-mongodbcds-pluginMongoDB as a native CAP database service, through Mongoose — CQN reads and writes, managed associations as ObjectId references, $expand resolved by populate, and cds deploy --to mongoose.independent, capMongoDB as a CAP database service through Mongoose
@cds-pgroll/postgres@cds-pgroll/postgrescliThe destructive half of PostgreSQL schema evolution — DROP and RENAME, which CAP's own schema_evolution: alter will not perform — driven from the command line beside @cap-js/postgres.independent, capCLI for DROP and RENAME schema changes beside @cap-js/postgres
@neoimpulse/cap-js-restore-model-defined-types@neoimpulse/cap-js-restore-model-defined-typescds-pluginA CAP plugin that casts values back to the types the CDS model declares after a READ, for the entities you name, where the database driver returned them as strings.independent, capCAP plugin casting read values back to CDS model types
@quadrio/cds-db2@quadrio/cds-db2cds-pluginA DB2 adapter for CDS, so a CAP model can be deployed to and served from DB2, last released July 2023 and still on npm while the repository it was published from has been deleted.independent, capDB2 adapter for CDS
@sap/cds-hana@sap/cds-hanacds-pluginThe SAP Cloud Application Programming Model's database adapter for SAP HANA, the package a CAP project adds to run its model on a SAP HANA database.sap official, capDatabase adapter for SAP HANA in CAP
@sap/cds@sap/cdspackageThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
@sap/hana-client@sap/hana-clientpackageSAP's own Node.js driver for SAP HANA: connect, run SQL and prepared statements, synchronously, through callbacks or as promises, over native client libraries npm installs per platform.sap official, btpSAP's Node.js driver for SAP HANA
SAP HANASAP HANAplatformSAP’s relational database platform, which stores application data and executes SQL and SQLScript in the database, available on-premise and as the managed service SAP HANA Cloud.sap official, btpSAP's relational database platform, on-premise and in HANA Cloud
cds-pgcds-pgcds-pluginA PostgreSQL adapter for SAP CDS, built by the SAP Mentors community, which gave CAP a Postgres persistence option years before @cap-js/postgres shipped.independent, capPostgreSQL adapter for SAP CDS from the SAP Mentors community
cap-snowflakecap-snowflakecds-pluginA CAP database adapter for Snowflake with OData V4 support, which the maintainer marks as early development, so its contract is expected to move.independent, capCAP database adapter for Snowflake with OData V4 support
cds-mysqlcds-mysqlcds-pluginA MySQL and MariaDB database adapter for CAP that connects to a database instance and translates incoming CQL/CQN requests to it; the repository the package declares has been deleted.independent, capMySQL and MariaDB database adapter for CAP
“Welcome to the base database service for [SAP Cloud Application Programming Model](https://cap.cloud.sap) Node.js. This service forms the core of all supported databases and is the base of our streamlined database architecture.” — cap-js/cds-dbs — db-service READMEchecked
The link named the root of a monorepo, so every crawl read the repository README — 'This is a monorepo for our SQL Database Services' — and filed it as this package's own: data/crawled/readmes/cap-js-db-service.md is that root README today. npm declares the directory as 'main/db-service', which the crawler cannot use as a path, so the subfolder URL is where it has to come from.
The entry named no registry page, so the only address it offered was a repository it shares with three other packages.
The repository's README states the relation: the four subfolders are parts of one monorepo, each published on its own.
Re-read on the package's own README in the repository — the document the subfolder link now resolves to — which carries the second sentence about forming the core of all supported databases as well.
Typed cds-plugin by placement, which defaults every candidate to that. It is not one.
The base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.
