Platform: Java
Packages
io.vertx.ceylon.sql
Dependencies
ceylon.json1.2.2
io.vertx.ceylon.core3.3.3
io.vertx.vertx-sql-common3.3.3
java.base (jvm)8
Values
noneshared none none

For engines that support it, none isolation means that each statement would essentially be its own transaction.

read_committedshared read_committed read_committed

Specifies that shared locks are held while the data is being read to avoid dirty reads, but the data can be changed before the end of the transaction, resulting in nonrepeatable reads or phantom data.

read_uncommittedshared read_uncommitted read_uncommitted

Implements dirty read, or isolation level 0 locking, which means that no shared locks are issued and no exclusive locks are honored. When this option is set, it is possible to read uncommitted or dirty data; values in the data can be changed and rows can appear or disappear in the data set before the end of the transaction. This is the least restrictive of the four isolation levels.

repeatable_readshared repeatable_read repeatable_read

Locks are placed on all data that is used in a query, preventing other users from updating the data, but new phantom rows can be inserted into the data set by another user and are included in later reads in the current transaction. Because concurrency is lower than the default isolation level, use this option only when necessary.

resultSetshared resultSet resultSet
serializableshared serializable serializable

Places a range lock on the data set, preventing other users from updating or inserting rows into the data set until the transaction is complete. This is the most restrictive of the four isolation levels. Because concurrency is lower, use this option only when necessary.

transactionIsolationshared transactionIsolation transactionIsolation
updateResultshared updateResult updateResult
Classes
ResultSetshared ResultSet

Represents the results of a SQL query.

It contains a list for the column names of the results, and a list of JsonArray - one for each row of the results.

SQLConnectionshared SQLConnection

Represents a connection to a SQL database

TransactionIsolationshared abstract TransactionIsolation

Represents a Transaction Isolation Level

UpdateResultshared UpdateResult

Represents the result of an update/insert/delete operation on the database.

The number of rows updated is available with getUpdated and any generated keys are available with getKeys.

noneshared none

For engines that support it, none isolation means that each statement would essentially be its own transaction.

read_committedshared read_committed

Specifies that shared locks are held while the data is being read to avoid dirty reads, but the data can be changed before the end of the transaction, resulting in nonrepeatable reads or phantom data.

read_uncommittedshared read_uncommitted

Implements dirty read, or isolation level 0 locking, which means that no shared locks are issued and no exclusive locks are honored. When this option is set, it is possible to read uncommitted or dirty data; values in the data can be changed and rows can appear or disappear in the data set before the end of the transaction. This is the least restrictive of the four isolation levels.

repeatable_readshared repeatable_read

Locks are placed on all data that is used in a query, preventing other users from updating the data, but new phantom rows can be inserted into the data set by another user and are included in later reads in the current transaction. Because concurrency is lower than the default isolation level, use this option only when necessary.

resultSetshared resultSet
serializableshared serializable

Places a range lock on the data set, preventing other users from updating or inserting rows into the data set until the transaction is complete. This is the most restrictive of the four isolation levels. Because concurrency is lower, use this option only when necessary.

transactionIsolationshared transactionIsolation
updateResultshared updateResult