Caching
On ABAP the platform's cache is the table buffer on the application server, configured per table and used without code; memoising anything else, such as the SCARR rows or cl_salv_table references in the examples of ABAP-CACHE-BOX, is written into the program.
Overview
Table buffering keeps rows of a database table in the shared memory of the application server, switched on and typed as single-record, generic or full buffering in the table's technical settings, and ABAP SQL reads use the buffer without code.
Not covered: At table rows. A value a program computes or an object it builds is not a table read, so holding it for reuse within the program is the program's own code.
Application-level memoisation: macros that generate a singleton cache class per data type or object type, backed by a hashed table.
Artifacts
Details
Coverage
For your agent
- Ref
capability:caching- JSON
- /capabilities/caching.json
- MCP
- Connecting an agent