• Overview of transactions: What is a transaction, using the transactions according to your requirements, etc.
• Principle: managing the transactions on HFSQL data files and special cases.
• Handling the transactions by programming.
• Managing the special cases (power outage, restoring the consistency of the database, etc).
• Advanced management: the files created during a transaction, management of computer identifier.

Versions 17 and later

This feature is now available for iPhone/iPad applications.

New in version 17

This feature is now available for iPhone/iPad applications.

This feature is now available for iPhone/iPad applications.

The management of transactions is available for the HFSQL Client/Server databases.

Using the transactions according to your requirements

• Perform the transactions in applications installed on reliable computers (surge protector, a single current application, ...): disk transaction
  In this case, the purpose of transactions is to be able to cancel a set of operations. It is possible to display windows in the middle of a transaction, to perform different lengthy processes, ...
  Each operation performed during the transaction is saved in a transaction file. The record used is locked in write mode until the transaction is validated or canceled.
• Perform trusted write operations in the data files (banking sector, accounting, ...).
  The transactions are used to insure the security of a set of operations. In this case, you must group all the write operations in your code in order to run them in a transaction. The code run during the transaction must display no window, must browse no data file, ... This code must only contain the operations for modifying the data files.
  Each operation performed during the transaction is saved in a transaction file. The record used is locked in write mode until the transaction is validated or canceled.

Principle of transactions on HFSQL data files

• The isolation mode of transactions is the "READ UNCOMMITED" mode.
• Versions 19 and later
  The isolation mode of transactions is defined by HTransactionIsolation. The default isolation mode is the "READ UNCOMMITED" mode.
  New in version 19
  The isolation mode of transactions is defined by HTransactionIsolation. The default isolation mode is the "READ UNCOMMITED" mode.
  The isolation mode of transactions is defined by HTransactionIsolation. The default isolation mode is the "READ UNCOMMITED" mode.
• Transactions are not available for Hyper File 5.5 data files.

Special cases

• Error in the program, the transaction is automatically abandoned.
• Call to EndProgram, the transaction is automatically abandoned.
• Test canceled from the editor, the transaction is automatically abandoned.
• Power outage or unexpected stop of the application (application stopped by the task manager for example):
  When the application is restarted, the consistency of the database can be restored:
  • By the WDTRANS tool (or WDOptimizer).
  • By the HFSQL Control Center.
  • During the first call to HTransactionStart.
  • By HTransactionCancel.

Special cases specific to HFSQL Client/Server:

• If the Client is lost, cancelation of the transaction.
• Restarting the server cancels the current transactions. Caution: the transaction is not canceled if the transaction applies to a data file with secure password. The transaction will be canceled during the next opening of the data file.

See Managing special cases for more details.