CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.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/sqlite
The SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.
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§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
Derived: the instrument's applicability matches this artifact, checked
§ 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.
§ 2Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
§ 3Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
Also, from Database connectors§ 1: 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.
What it declares
Every artifact
Type
CDS plugin
Origin
By SAP
As a CDS plugin
Declared for
^10
declared, the peer range, as published
Distributed through
npm
declared, How the plugin is installed into a CAP project, as its documentation says., read npm add @cap-js/sqlite -D — @cap-js/sqlite — README, 2026-10-18
Connections8
Group by8 of 8 connections
NodeRelationConditionBasis
Functional1
Database connectorsDatabase connectorscapabilityConnecting a data model and its queries to a databaseSAP and community, narrow by design
→provides
Auto-configures an in-memory SQLite database for the development profile through the cds-plugin technique, a persistent file when configured, and since @sap/cds 10.1.0 the sqlite:memory preset in any profile.
provides Database connectors
Functional, stated
For
Auto-configures an in-memory SQLite database for the development profile through the cds-plugin technique, a persistent file when configured, and since @sap/cds 10.1.0 the sqlite:memory preset in any profile.
Basis
“The @cap-js/sqlite package uses the cds-plugin technique to auto-configure your application for using an in-memory SQLite database by default for the development profile.”Using SQLite for Development — capire, checked
stated
provides Database connectors
Functional, stated
For
Auto-configures an in-memory SQLite database for the development profile through the cds-plugin technique, a persistent file when configured, and since @sap/cds 10.1.0 the sqlite:memory preset in any profile.
Basis
“The @cap-js/sqlite package uses the cds-plugin technique to auto-configure your application for using an in-memory SQLite database by default for the development profile.”Using SQLite for Development — capire, checked
Connecting a data model and its queries to a database
Technical6
@cap-js/ai@cap-js/aicds-pluginValue-help recommendations and SAP AI Core as a CAP servicesap official, cap
←optionally used by
if The local vector embeddings are used: capire states the plugin requires @sap/cds ^10.1 and @cap-js/sqlite ^3.1 for them. The recommendations and the AICore service do not involve SQLite
optionally used by @cap-js/ai
Technical, derived, through inverted from its requires edge
If
The local vector embeddings are used: capire states the plugin requires @sap/cds ^10.1 and @cap-js/sqlite ^3.1 for them. The recommendations and the AICore service do not involve SQLite.
For
The database the plugin redirects so that the vector functions run against a local ONNX model instead of the character-hash emulation.
Basis
“It requires `@sap/cds` `^10.1` and `@cap-js/sqlite` `^3.1`, and is experimental and intended for local development only.”CAP-native Embeddings, SQLite and H2 — capire, source on GitHub, checked
derived
optionally used by @cap-js/ai
Technical, derived, through inverted from its requires edge
If
The local vector embeddings are used: capire states the plugin requires @sap/cds ^10.1 and @cap-js/sqlite ^3.1 for them. The recommendations and the AICore service do not involve SQLite.
For
The database the plugin redirects so that the vector functions run against a local ONNX model instead of the character-hash emulation.
Basis
“It requires `@sap/cds` `^10.1` and `@cap-js/sqlite` `^3.1`, and is experimental and intended for local development only.”CAP-native Embeddings, SQLite and H2 — capire, source on GitHub, checked
Value-help recommendations and SAP AI Core as a CAP service
cds-cachingcds-cachingcds-pluginCAP caching plugin for query results and remote service responsesindependent, cap
←optionally used by
when the SQLite store is selected
optionally used by cds-caching
Technical, derived, through inverted from its requires edge
If
When the SQLite store is selected.
For
The README requirements table specifies ^1 with cds 8, ^2 with cds 9, and ^3 with cds 10.
Basis
“`@cap-js/sqlite` (SQLite store) | `^1` on cds 8, `^2` on cds 9, `^3` on cds 10”cds-caching — Requirements, checked
derived
optionally used by cds-caching
Technical, derived, through inverted from its requires edge
If
When the SQLite store is selected.
For
The README requirements table specifies ^1 with cds 8, ^2 with cds 9, and ^3 with cds 10.
Basis
“`@cap-js/sqlite` (SQLite store) | `^1` on cds 8, `^2` on cds 9, `^3` on cds 10”cds-caching — Requirements, checked
CAP caching plugin for query results and remote service responses
ui5-cap-serverside-rendering-demoui5-cap-serverside-rendering-demosampleDemo CAP bookshop with server-rendered UI5 viewsindependent, cap
←optionally used by
if the project is run locally rather than deployed
optionally used by ui5-cap-serverside-rendering-demo
Technical, derived, through inverted from its requires edge
If
the project is run locally rather than deployed
For
The database the project reads `db/data/my.bookshop-Books.csv` into while it is run locally.
Data federation for CAP via delegation, caching and replication
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
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/db-service@cap-js/db-servicepackageThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.sap official, capBase service shared by CAP's SQLite, PostgreSQL and HANA services
@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-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 SQLite database service for [SAP Cloud Application Programming Model](https://cap.cloud.sap) Node.js, based on streamlined database architecture and [*better-sqlite* driver](https://www.npmjs.com/package/better-sqlite3).” — cap-js/cds-dbs — sqlite 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-sqlite.md is that root README today. npm's record for @cap-js/sqlite declares no repository directory, so the subfolder URL is the only place it can come from, and it is the form the corpus already uses for a package inside a monorepo.
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.
https://github.com/cap-js/cds-dbs/tree/main/sqlite — 'Welcome to the SQLite database service for SAP Cloud Application Programming Model Node.js, based on streamlined database architecture and better-sqlite driver.'
The SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.
