|
|
|
|
|
|
|
|
|
|
|
|
| Resultados de la búsqueda |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The USE ... IN statement is used to define the block of operations to be performed in a transaction. |
|
|
|
|
|
|
|
| Declares a transaction savepoint. |
|
|
|
|
|
|
|
| Rolls the transaction back to the savepoint. |
|
|
|
|
|
|
|
| Declares a transaction savepoint. |
|
|
|
|
|
|
|
| Rolls the transaction back to the savepoint. |
|
|
|
|
|
|
|
| Enables or disables the management of transactions for one or more files. |
|
|
|
|
|
|
|
| Starting with version 21, you can manage transactions in SQL code... |
|
|
|
|
|
|
|
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) described in the data model editor or by HOpenConnection.
|
|
|
|
|
|
|
|
| Starts a transaction on the data files (HFSQL or accessed via a Native Connector) and creates the transaction file. |
|
|
|
|
|
|
|
| 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. |
|
|
|
|
|
|
|
| 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... |
|
|
|
|
|
|
|
| Used to find out whether a transaction is in progress. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|