PostgreSQL persistence adapter for CAP (Node.js)
The contradiction the adapter was built to resolve, stated plainly in 2020: CAP's core is open, non-intrusive and platform-agnostic, which is what would let it run outside SAP's world — except that HANA was the only officially supported production persistence and HANA exists only inside BTP. cds-pgcds-pgA 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, cap is the answer to that, and this is the post that argues for it. Read now as the front end of a story whose other end is the 2023 post recording cds-pg's deprecation in favour of @cap-js/postgres.
Where it sits
Who is behind it
In the atlas: maintains 7, contributes to 53, wrote 2@vobuauthor
Before you read it
read from the pageApplicabilitySupersededcds-pg is archived. @cap-js/postgres answers the same capability.
This is a derived prompt to re-check the work, not a claim that the work is wrong. Exact stale statements are recorded separately after editorial review.
Properties
About this work
What was found on the page
For database-connectors
Details
Graph
Source
History
- explains → applies_to on capability:database-connectorsDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).
- Entered the atlasDiscovered via SAP Community · cap-tag.
For your agent
- Ref
content:postgresql-persistence-adapter-for-cap-nodejs- JSON
- /content/postgresql-persistence-adapter-for-cap-nodejs.json
- MCP
- Connecting an agent