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 →

com.sap.cds:cds-feature-postgresql

The 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.

Adds PostgreSQL as a datasource for a CAP Java application built on com.sap.cds:cds-services-bom. Added as a runtime-scoped Maven dependency, it auto-configures the default Persistence Service from a bound PostgreSQL instance and lets cds deploy --to postgres --dry generate the schema.sql Spring runs on startup. PostgreSQL is supported in addition to SAP HANA; capire lists limitations in comparison, schema evolution first among them, and multitenancy and extensibility are not yet supported on it. On SAP BTP, Cloud Foundry only the community java_buildpack can consume a PostgreSQL service from a CAP Java application, and the buildpack's own datasource initialization has to be disabled so CAP Java creates the datasource instead. The Node.js counterpart is @cap-js/postgres.

Facts

LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP

Where it sits

Lives in
Provides
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).
Flavors
Requires
PostgreSQLPostgreSQLoutside the atlasNamed as a dependency in its documentation.

Before choosing this

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.
  • § 1 License. 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.

SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
Package
Origin
By SAP
Runtime
Java

As a package

Where it runs
does not say
Distributed through
does not say

Connections3

Where it sits in your app

Download
Your CAP applicationdocumentedrequiresPostgreSQL, systemPostgreSQLsystemcom.sap.cds:cds-feature-postgresql, modulecom.sap.cds:cds-feat…
SAPnot SAP's, or the project's owndocumented only
Database connectors
  1. SAP ASE ServiceManaged SAP ASE databases on BTP for Java applicationsfrom BTP/BAIP
  2. SAP HANA CloudManaged SAP HANA database service on BTPfrom BTP/BAIP
  3. SAP HANA Service (SAP Regions) for SAP BTPManaged SAP HANA 2.0 databases in fixed sizes on SAP BTPfrom BTP/BAIP
  4. PostgreSQL on SAP BTP, hyperscaler optionManaged PostgreSQL from the hyperscaler via a BTP service bindingfrom BTP/BAIP
  5. com.sap.cds:cds-feature-hanaSAP HANA Cloud datasource for CAP Java applicationsfrom CAP
  6. com.sap.cds:cds-feature-jdbcJDBC runtime for H2 and SQLite in CAP Javafrom CAP
  7. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versionsfrom CAP
  8. @cap-js/db-serviceBase service shared by CAP's SQLite, PostgreSQL and HANA servicesfrom CAP
  9. @cap-js/hanaSAP HANA database service for CAPfrom CAP
  10. @cap-js/postgresPostgreSQL database service for CAPfrom CAP
  11. @cap-js/sqliteSQLite database service for CAP, in memory during developmentfrom CAP
  12. cap-postgres-btp-connectivityTunnels CAP Node.js to a private PostgreSQL via Cloud Connectorfrom CAP
  13. cds-mongodbMongoDB as a CAP database service through Mongoosefrom CAP
  14. @cds-pgroll/postgresCLI for DROP and RENAME schema changes beside @cap-js/postgresfrom CAP
  15. hdbPure JavaScript SAP HANA driver for Node.jsfrom BTP/BAIP
  16. @neoimpulse/cap-js-restore-model-defined-typesCAP plugin casting read values back to CDS model typesfrom CAP
  17. @quadrio/cds-db2DB2 adapter for CDSfrom CAP
  18. @sap/cds-hanaDatabase adapter for SAP HANA in CAPfrom CAP
  19. @sap/cdsCAP Node.js runtimefrom CAP
  20. @sap/hana-clientSAP's Node.js driver for SAP HANAfrom BTP/BAIP
  21. SAP HANASAP's relational database platform, on-premise and in HANA Cloudfrom BTP/BAIP
  22. SAP-samples/hana-hdbext-promisfied-examplePromise-based wrappers around the SAP HANA client librariesfrom BTP/BAIP
  23. cds-pgPostgreSQL adapter for SAP CDS from the SAP Mentors communityfrom CAP
  24. cap-snowflakeCAP database adapter for Snowflake with OData V4 supportfrom CAP
  25. cds-mysqlMySQL and MariaDB database adapter for CAPfrom CAP

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesjava
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, data-and-persistence
Flavors1
Java
“CAP Java comes with a rich set of prepared modules for all different layers of the stack:” — Building Applications — capirechecked
History in the atlas2
  1. Auto-configures the default Persistence Service from a bound PostgreSQL instance so a CAP Java application runs against PostgreSQL instead of SAP HANA, with known limitations in schema evolution and no multitenancy or extensibility support yet.
  2. First seen.
For your agent
Ref
artifact:cap-java-cds-feature-postgresql
JSON
/artifacts/cap-java-cds-feature-postgresql.json
MCP
Connecting an agent