Uses of Package
com.kingsrook.qqq.backend.core.model.actions.consistentread

Packages that use com.kingsrook.qqq.backend.core.model.actions.consistentread

Package	Description
com.kingsrook.qqq.backend.core.actions
com.kingsrook.qqq.backend.core.model.actions.consistentread
com.kingsrook.qqq.backend.core.modules.backend
com.kingsrook.qqq.backend.core.modules.backend.implementations.memory
com.kingsrook.qqq.backend.module.mongodb
com.kingsrook.qqq.backend.module.mongodb.actions
com.kingsrook.qqq.backend.module.postgres.strategy	PostgreSQL-specific RDBMS action strategies.
com.kingsrook.qqq.backend.module.rdbms
com.kingsrook.qqq.backend.module.rdbms.actions
com.kingsrook.qqq.backend.module.rdbms.strategy
com.kingsrook.qqq.backend.module.sqlite.strategy

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.core.actions

Class	Description
ConsistencyGuarantee	What a consistent-read transaction actually guarantees - to be recorded by callers (e.g., in a backup manifest) rather than assumed.
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.core.model.actions.consistentread

Class	Description
ConsistencyGuarantee	What a consistent-read transaction actually guarantees - to be recorded by callers (e.g., in a backup manifest) rather than assumed.
ConsistencyScope	How far apart in time a consistent-read transaction allows the reads of different tables in the same backend to be.
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.core.modules.backend

Class	Description
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.core.modules.backend.implementations.memory

Class	Description
ConsistencyGuarantee	What a consistent-read transaction actually guarantees - to be recorded by callers (e.g., in a backup manifest) rather than assumed.
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.mongodb

Class	Description
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.mongodb.actions

Class	Description
ConsistencyGuarantee	What a consistent-read transaction actually guarantees - to be recorded by callers (e.g., in a backup manifest) rather than assumed.

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.postgres.strategy

Class	Description
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.rdbms

Class	Description
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.rdbms.actions

Class	Description
ConsistencyGuarantee	What a consistent-read transaction actually guarantees - to be recorded by callers (e.g., in a backup manifest) rather than assumed.
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.rdbms.strategy

Class	Description
ConsistencyGuarantee	What a consistent-read transaction actually guarantees - to be recorded by callers (e.g., in a backup manifest) rather than assumed.
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).

Classes in com.kingsrook.qqq.backend.core.model.actions.consistentread used by com.kingsrook.qqq.backend.module.sqlite.strategy

Class	Description
ConsistentReadInput	Input for QBackendModuleInterface.openConsistentReadTransaction - asks a backend for a read-only transaction through which every table read reflects one instant (see ConsistencyScope).