Uses of Record Class
com.kingsrook.qqq.backend.module.rdbms.strategy.ConsistentReadStart
Packages that use ConsistentReadStart
Package
Description
PostgreSQL-specific RDBMS action strategies.
-
Uses of ConsistentReadStart in com.kingsrook.qqq.backend.module.postgres.strategy
Methods in com.kingsrook.qqq.backend.module.postgres.strategy that return ConsistentReadStartModifier and TypeMethodDescriptionPostgreSQLRDBMSActionStrategy.beginConsistentRead(Connection connection, ConsistentReadInput input) PostgreSQL: REPEATABLE READ (READ ONLY, if so requested) - so every table reflects the one snapshot the transaction takes at its first statement. -
Uses of ConsistentReadStart in com.kingsrook.qqq.backend.module.rdbms.strategy
Methods in com.kingsrook.qqq.backend.module.rdbms.strategy that return ConsistentReadStartModifier and TypeMethodDescriptionBaseRDBMSActionStrategy.beginConsistentRead(Connection connection, ConsistentReadInput input) MySQL/MariaDB (InnoDB): START TRANSACTION WITH CONSISTENT SNAPSHOT (READ ONLY).default ConsistentReadStartRDBMSActionStrategyInterface.beginConsistentRead(Connection connection, ConsistentReadInput input) Start a transaction on the (autocommit-off) connection, such that every read through it sees one snapshot - or, for a database with no better way, at least asks for REPEATABLE READ isolation, and reports BEST_EFFORT. -
Uses of ConsistentReadStart in com.kingsrook.qqq.backend.module.sqlite.strategy
Methods in com.kingsrook.qqq.backend.module.sqlite.strategy that return ConsistentReadStartModifier and TypeMethodDescriptionSQLiteRDBMSActionStrategy.beginConsistentRead(Connection connection, ConsistentReadInput input) SQLite: with autocommit off, the driver issues BEGIN (deferred), and the first read - which we do here, so the snapshot is taken now rather than at the caller's first query - takes the read lock/snapshot.