Temporal data
Keeping every version of a record that was valid for a period, and reading the one that held at a given moment — the assignment somebody had on the first of March, not the one they have now — without the application filtering time slices by hand.
Overview
Not covered: At the read. Writing a time slice is a custom handler of the application's own, SQLite serves no time-travel or time-period query because it has no session variables, and a time-period query that expands across two temporal entities needs care the guide spells out. The guide names neither runtime, so which flavor serves it is what the artifacts state and no more. Nothing outside the core is mapped here yet.
Built into @sap/cds
No community artifact is documented here.
Artifacts
Content
Group by
Piece, what it offers
My CAP Projects ToolboxMy CAP Projects ToolboxA working inventory of daily CAP tooling: scaffolding a project with cds init and growing it facet by facet through cds add (TypeScript, seed data, an .http test file, a handler stub), then running it with cds watch and setting a breakpoint in a custom handler from SAP Business Application Studio's JavaScript Debug Terminal. It also walks through an @open entity that accepts properties the model never declared, and reading temporal data defined with CAP's temporal aspect, where a plain read returns only what is valid now and a custom handler is needed to retrieve every time slice.vvdries, published 2024-12-23
Details
Coverage
For your agent
- Ref
capability:temporal-data- JSON
- /capabilities/temporal-data.json
- MCP
- Connecting an agent