- * The simplest usage of a Configuration instance is to use it
- * exactly for a single Query execution, disposing it immediately.
- * This will make it very simple to implement thread-safe behaviour.
- *
- * At the same time, jOOQ does not require Configuration instances
- * to be that short-lived. Thread-safety will then be delegated to component
- * objects, such as the {@link ConnectionProvider}, the {@link ExecuteListener}
- * list, etc.
- *
* A Configuration is composed of types composing its state and of
* SPIs:
*
+ *
+ * The simplest usage of a Configuration instance is to use it
+ * exactly for a single Query execution, disposing it immediately.
+ * This will make it very simple to implement thread-safe behaviour, but
+ * reflection caches will not be used optimally, e.g. when using
+ * {@link DefaultRecordMapper}.
+ *
+ * At the same time, jOOQ does not require Configuration instances
+ * to be that short-lived. Thread-safety will then be delegated to component
+ * objects, such as the {@link ConnectionProvider}, the {@link ExecuteListener}
+ * list, etc.
+ *
+ * For a {@link Configuration} to be used in a thread safe way, all
+ * set() methods must be avoided post initialisation, and
+ * {@link #settings()} must not be modified either. If you wish to create a
+ * derived configuration for local usage, with some configuration parts changed,
+ * use the various derive() methods, instead.
*
* @author Lukas Eder
*/