Should we enable soda metadata cache?

[RichardExley]

Found this in node-oracledb doc:

3.3.1.1.19 sodaMetaDataCache

Boolean sodaMetaDataCache
Indicates whether the pool’s connections should share a cache of SODA metadata. This improves SODA performance by reducing round-trips to the database when opening collections. It has no effect on non-SODA operations.

The default is false.

There is no global equivalent for setting this attribute. SODA metadata caching is restricted to pooled connections only.

Note: if the metadata of a collection is changed externally, the cache can get out of sync. If this happens, the cache can be cleared by calling pool.reconfigure({ sodaMetadataCache: false }). A second call to reconfigure() should then be made to re-enable the cache.

This property was added in node-oracledb 5.2. It requires Oracle Client 21.3 (or later). The feature is also available in Oracle Client 19c from 19.11 onward.

I assume there is similar functionality for the other DB APIs. Do we need this for order-helidon, for example?