ABAP Keyword Documentation → ABAP − Reference → Processing External Data → ABAP Database Access → ABAP SQL → ABAP SQL - Overview → ABAP SQL - Table Buffering → Table Buffering - Buffering Types
Table Buffering - Single Record Buffering
Only those rows in the table are buffered that are actually accessed. This requires less space in the buffer than when using generic or full buffering. On the other hand, more administration work is required and significantly more direct database accesses.
If a WHERE clause is used to access
a non-buffered row and this clause specifies equality conditions joined using AND,
an attempt is made to load this row. If the row is not found, this is noted in the buffer and a fully specified WHERE clause is used to avoid a new database access in the next read.
Other versions:
7.31 | 7.40 | 7.54
Notes
- When using single record buffering, any ABAP SQL statements must respect the full primary key to prevent them from bypassing table buffering.
- Single record buffering is recommended for large tables from which single rows are often read. In smaller tables from which many rows are read, full buffering is usually preferred since this reduces the number of direct database accesses that need to be loaded.
- The use of single record buffering is specified by the
WHEREclause only and not by using the additionSINGLE.