[jOOQ/jOOQ#18897] Add information about the lack of thread safety in Meta implementations to Meta Javadoc
This commit is contained in:
parent
6c46ea882a
commit
7a6efe74db
@ -90,7 +90,12 @@ import org.jetbrains.annotations.NotNull;
|
||||
* </ol>
|
||||
* <p>
|
||||
* This type is a {@link Scope} with independent lifecycle and its own
|
||||
* {@link #data()} map.
|
||||
* {@link #data()} map. Its implementations are not required to be thread safe
|
||||
* and are likely not. Clients should access separate instances per thread and
|
||||
* use-case. Implementations are allowed to cache meta data for faster
|
||||
* subsequent access, e.g. by means of {@link #snapshot()}. Clients should
|
||||
* assume that meta data is not up to date if other processes alter the database
|
||||
* at the same time as clients access this API.
|
||||
*
|
||||
* @author Lukas Eder
|
||||
*/
|
||||
|
||||
Loading…
Reference in New Issue
Block a user