|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Starts a transaction on the data files (HFSQL or accessed via Native Access) and creates the transaction file. |
|
|
|
|
|
|
|
| WDOptimizer is used to ... |
|
|
|
|
|
|
|
| The USE ... IN statement is used to define the block of operations to be performed in a transaction. |
|
|
|
|
|
|
|
| The various operations that can be carried out with WDOptimizer are ... |
|
|
|
|
|
|
|
| Declares a transaction savepoint. |
|
|
|
|
|
|
|
| To keep maximum compatibility between HFSQL Classic applications (single-user or multi-user) and HFSQL Client/Server applications, the transaction mechanism in HFSQL Client/Server mode is similar to the one in HFSQL Classic mode... |
|
|
|
|
|
|
|
| If a transaction is in progress, rolls back all operations performed on data files in transactions since the start of the transaction. |
|
|
|
|
|
|
|
Validates the current transaction: - the modifications performed on the data file since the start of transaction (HTransactionStart) are validated.
- the transaction file is deleted (if the transaction is the last transaction in progress for a network application)
- the records locked in read-only by the transaction are unlocked.
|
|
|
|
|
|
|
|
| When using a database, you may have to perform maintenance operations on the data files... |
|
|
|
|
|
|
|
| Enables or disables the management of transactions for one or more files. |
|
|
|
|
|
|
|
| This chapter covers the following topics... |
|
|
|
|
|
|
|
| The HFSQL engine proposes to isolate the transactions... |
|
|
|
|
|
|
|
| Rolls the transaction back to the savepoint. |
|
|
|
|
|
|
|
| Transforms all "in transaction" records into "normal" records if they do not belong to a transaction currently in progress. |
|
|
|
|
|
|
|
| Declares a transaction savepoint. |
|
|
|
|
|
|
|
| Enables or disables the management of transactions for one or more files. |
|
|
|
|
|
|
|
| Transforms all "in transaction" records into "Normal" records if they do not belong to an ongoing transaction. |
|
|
|
|
|
|
|
| Rolls the transaction back to the savepoint. |
|
|
|
|
|
|
|
Validates the current transaction: - the modifications performed on the data file since the start of transaction (HTransactionStart) are validated.
- the transaction file is deleted (if the transaction is the last transaction in progress for a network application)
- the records locked in read-only by the transaction are unlocked.
|
|
|
|
|
|
|
|
| Starts a transaction on the data files (HFSQL or accessed via a Native Connector) and creates the transaction file. |
|
|
|
|
|
|
|
| If a transaction is active, rolls back all changes made to the data files since the beginning of the transaction. |
|
|
|
|
|
|
|
| Used to find out whether a transaction is in progress. |
|
|
|
|
|
|
|
Begins, commits or rolls back a transaction:- on the files of a database opened by SQLConnect,
- on the files of a database opened by a connection (OLE DB or Native Access/Native Connector) defined in the data model editor or with HOpenConnection.
|
|
|
|
|
|
|
|
| Configures the isolation level of transactions for a connection to an HFSQL server. |
|
|
|
|
|
|
|
| Used to find out whether a transaction was interrupted (the transaction was neither validated nor canceled). |
|
|
|
|
|
|
|
| Starts a transaction on the data files (HFSQL or accessed via a Native Connector) and creates the transaction file. |
|
|
|
|
|
|
|
| Configures the isolation level of transactions for a connection to an HFSQL server. |
|
|
|
|
|
|
|
| Starting with version 21, you can manage transactions in SQL code... |
|
|
|
|
|
|
|
| Starts a transaction on the data files (HFSQL or accessed via Native Access) and creates the transaction file. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|