public abstract class StartTransactionMessageType extends ServerInputMessageType
Modifier and Type | Field and Description |
---|---|
static int |
MESSAGETYPEID
The numeric ID for messages of this type (1367873380 )
|
Modifier and Type | Method and Description |
---|---|
StartTransactionMessage |
message(java.lang.String userID,
boolean userAuthenticatedByClient,
java.lang.String signatureAlgorithm,
byte[] signature)
Deprecated.
deprecated
|
StartTransactionMessage |
message(java.lang.String userID,
boolean userAuthenticatedByClient,
java.lang.String signatureAlgorithm,
byte[] signature,
boolean readOnlyTransaction,
boolean autoCommit)
Deprecated.
deprecated
|
StartTransactionMessage |
message(java.lang.String userID,
boolean userAuthenticatedByClient,
java.lang.String signatureAlgorithm,
byte[] signature,
boolean readOnlyTransaction,
boolean autoCommit,
DDLCapture captureDDL)
Deprecated.
deprecated
|
abstract StartTransactionMessage |
message(java.lang.String userID,
boolean userAuthenticatedByClient,
java.lang.String signatureAlgorithm,
byte[] signature,
boolean readOnlyTransaction,
boolean autoCommit,
DDLCapture captureDDL,
SnapShotIsolationMode snapShotIsolationMode)
Factory method for getting a StartTransactionMessage of this MessageType's version, holding the given data
|
public static final int MESSAGETYPEID
public abstract StartTransactionMessage message(java.lang.String userID, boolean userAuthenticatedByClient, java.lang.String signatureAlgorithm, byte[] signature, boolean readOnlyTransaction, boolean autoCommit, DDLCapture captureDDL, SnapShotIsolationMode snapShotIsolationMode)
userID
- The identification of the user owning the new transactionuserAuthenticatedByClient
- indicates whether the user owning the new transaction has been authenticated by the clientsignatureAlgorithm
- name of the user authentication algorithm to be used by the server if the decides that it will do user authentication itselfsignature
- The signature to be verified by the server if the decides that it will do user authentication itselfreadOnlyTransaction
- flag indicating whether or not the new transaction is a read-only one, i.e. whether it will or will not attempt updates to the database. Must be false if this message is sent to a server prior to 1.2autoCommit
- flag indicating whether each individual statement is automatically committed (meaning, for a read-only transaction, that locks will immediately be released when the statement completes)captureDDL
- flag indicating whether any DDL executed in this transaction should be captured by the server in a script. If set, a script file will be created by the server holding all the DDL executed in this transaction. For anonymous transactions, the file will be written in the server's user.home directory, and will be given the name of the internal transaction ID, followed by "DDL.SPS". For non-anonymous transactions, a directory will be created in the server's user.home directory, named after the user owning the transaction, and the script file will be written in that directory.snapShotIsolationMode
- The snapshot isolation mode that this readonly transaction is to run under (snapshot isolation does not apply to update transactions. Update transactions always run in SnapShotIsolatinMode.OFF).@Deprecated public final StartTransactionMessage message(java.lang.String userID, boolean userAuthenticatedByClient, java.lang.String signatureAlgorithm, byte[] signature, boolean readOnlyTransaction, boolean autoCommit, DDLCapture captureDDL)
userID
- The identification of the user owning the new transactionuserAuthenticatedByClient
- indicates whether the user owning the new transaction has been authenticated by the clientsignatureAlgorithm
- name of the user authentication algorithm to be used by the server if the decides that it will do user authentication itselfsignature
- The signature to be verified by the server if the decides that it will do user authentication itselfreadOnlyTransaction
- flag indicating whether or not the new transaction is a read-only one, i.e. whether it will or will not attempt updates to the database. Must be false if this message is sent to a server prior to 1.2autoCommit
- flag indicating whether each individual statement is automatically committed (meaning, for a read-only transaction, that locks will immediately be released when the statement completes)captureDDL
- flag indicating whether any DDL executed in this transaction should be captured by the server in a script. If set, a script file will be created by the server holding all the DDL executed in this transaction. For anonymous transactions, the file will be written in the server's user.home directory, and will be given the name of the internal transaction ID, followed by "DDL.SPS". For non-anonymous transactions, a directory will be created in the server's user.home directory, named after the user owning the transaction, and the script file will be written in that directory.@Deprecated public final StartTransactionMessage message(java.lang.String userID, boolean userAuthenticatedByClient, java.lang.String signatureAlgorithm, byte[] signature, boolean readOnlyTransaction, boolean autoCommit)
userID
- The identification of the user owning the new transactionuserAuthenticatedByClient
- indicates whether the user owning the new transaction has been authenticated by the clientsignatureAlgorithm
- name of the user authentication algorithm to be used by the server if the decides that it will do user authentication itselfsignature
- The signature to be verified by the server if the decides that it will do user authentication itselfreadOnlyTransaction
- flag indicating whether or not the new transaction is a read-only one, i.e. whether it will or will not attempt updates to the database. Must be false if this message is sent to a server prior to 1.2autoCommit
- flag indicating whether each individual statement is automatically committed (meaning, for a read-only transaction, that locks will immediately be released when the statement completes)@Deprecated public final StartTransactionMessage message(java.lang.String userID, boolean userAuthenticatedByClient, java.lang.String signatureAlgorithm, byte[] signature)
userID
- The identification of the user owning the new transactionuserAuthenticatedByClient
- indicates whether the user owning the new transaction has been authenticated by the clientsignatureAlgorithm
- name of the user authentication algorithm to be used by the server if the decides that it will do user authentication itselfsignature
- The signature to be verified by the server if the decides that it will do user authentication itself