-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines
This is a followup task for WT-11126. The compile_configuration API in that ticket returns a pointer to an internal char* "dummy string" buffer. The result can really only be used by the caller as an opaque pointer, and calling it a char * is confusing. We should investigate returning something like a string like "~57". It can be copied as a normal string and later used. Instead of checking the address, we check the content, in this case it would refer to the 57th entry in the compiled table. The "~" signifies it is a reference to a compiled string, so we don't treat it as a configuration string.
One benefit is making it easier for Python to work with compile_configuration/bind_configuration. Another benefit is that it may be easier to understand conceptually. A final benefit is that there would be no limit on the number of preconfigured configurations.
- related to
-
WT-11126 Add configuration compilation to speed up WT_SESSION::begin_transaction
- Closed