|
|
|
|
|
|
|
Immediately runs a scheduled task regardless of its schedule:
stored procedure,
backup,
optimization,
refresh of materialized view.... |
|
|
|
|
|
|
Retrieves locally the content of a compressed backup (in ZIP format) performed on an HFSQL server. |
|
|
|
|
|
|
Declares a transaction savepoint. |
|
|
|
|
|
|
Lists the scheduled tasks defined on an HFSQL server:
stored procedure,
backup,
optimization,
refresh of materialized view.... |
|
|
|
|
|
|
Defines the password used to create or open a data file. |
|
|
|
|
|
|
Defines the password used to create or open a data file. |
|
|
|
|
|
|
List of functions for HFSQL management... |
|
|
|
|
|
|
Used to find out whether a transaction was interrupted (the transaction was neither validated nor canceled). |
|
|
|
|
|
|
List of functions for HFSQL management... |
|
|
|
|
|
|
Changes the path to a data file (i.e. directory in which the file will be handled). |
|
|
|
|
|
|
Transforms all "in transaction" records into "Normal" records if they do not belong to an ongoing transaction. |
|
|
|
|
|
|
Dynamically changes the connection associated with a data file. |
|
|
|
|
|
|
Enables or disables the management of transactions for one or more files. |
|
|
|
|
|
|
Enables or disables the management of transactions for one or more files. |
|
|
|
|
|
|
Dynamically changes the connection associated with a data file. |
|
|
|
|
|
|
Changes the path to a data file (i.e. directory in which the file will be handled). |
|
|
|
|
|
|
Starts a transaction on the data files (HFSQL or accessed via Native Access) and creates the transaction file. |
|
|
|
|
|
|
Transforms all the records "in transaction" into "Normal" records if these records do not belong to a transaction currently in progress. |
|
|
|
|
|
|
If a transaction is in progress, cancels all the operations performed on the data files in transaction since the start of 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.... |
|
|
|
|
|
|
Starts a transaction on the data files (HFSQL or accessed via Native Access) and creates the transaction file. |
|
|
|
|
|
|
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. |
|
|
|
|
|
|
Once the User Groupware is configured, the configuration of users and accesses is performed at runtime, by connecting with a "supervisor" account...... |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|