Feature: Implement config definition caching within a transaction

[tobiemh]

Is your feature request related to a problem?

Currently within a transaction, TABLE definitions, EVENT definitions, FIELD definitions, INDEX definitions, and foreign TABLE AS definitions are fetched for every record when reading or writing records.

Ideally we should only fetch the definitions once, and then use the cached values when fetching them for subsequent record processing.

Describe the solution

Use an in-transaction cache to store and cache configuration table records once they have been retrieved for the first time within a transaction.

This can be used when retrieving:

DEFINE TABLE statements for the document table
DEFINE EVENT statements for the document events
DEFINE FIELD statements for the document fields
DEFINE INDEX statements for the document indexes
DEFINE TABLE AS statements for the document foreign tables

Alternative methods

No alternative methods.

SurrealDB version

surreal 1.0.0-beta.5 for macos on aarch64

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct