Which database the model actually runs on, and what changes when it is not the default one — the choice that is invisible until a query behaves differently. HANA Cloud is the default under a CAP application: HDI containers, calculation views, and the features the core reaches for first. PostgreSQLPostgreSQLA 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. through @cap-js/postgres@cap-js/postgresThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, cap is the alternative when the answer is not HANA, with its own schema evolution and no HDI.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
The PostgreSQL database service for CAP Node.js, on the same database services architecture as the SQLite and SAP HANA services; CAP Java runs on PostgreSQL through its own JDBC feature.
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.
Defines cds.DatabaseService, the technical service every database package subclasses, and auto-wires the installed one, SQLite, SAP HANA or PostgreSQL, for the active profile.
A Node.js coverage assessment has not been written. View all flavors
A Node.js coverage assessment has not been written. View all flavors
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.
SAP Developer License Agreement 3.2 CAP →Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
The sqlite:memory preset configures an in-memory SQLite database in all profiles, including production, for edge cases such as an in-memory cache. Before, SQLite was the development and test database and production meant SAP HANA or PostgreSQL.
Advice that SQLite cannot be configured for the production profile at all.
Before cds8, @cap-js/sqlite and @cap-js/postgres were beta previews of a new database-service architecture begun in cds7, and PostgreSQL support in practice meant the community's cds-pg adapter. cds8 concluded that rewrite: @cap-js/sqlite, @cap-js/postgres and @cap-js/hana all reached general availability and became the defaults, sharing one query-translation layer. The 8 line reached npm on 2024-07-12; 8.0.3 was its first published release.
Setup guidance that adds cds-pg for PostgreSQL or treats the @cap-js database services as beta-only. cds-pg was archived in July 2023 in favour of @cap-js/postgres, and since cds8 the @cap-js services are what a new project gets by default.
capability:database-connectors