|
|
|
|
|
- Managing locks
- HSecurity and HFlush
HFlush (Function) In french: HForceEcriture
Available only with these kinds of connection
Forces the operating system of the computer where the data files are found to write data onto the disk. The HFSQL context of the manipulated data file is preserved (blocking, current path, etc.). Remark: Used regularly, this function minimizes data loss caused by unexpected stoppages of the workstation on which the data files are stored (e.g. power failure).
Client.Nom = "Moulin"
Client.Prenom = "François"
Client.Adresse = "Impasse de la belle"
Client.Ville = "Montpellier"
Client.CodeP = "34000"
Client.Pays = "France"
HAdd(Client)
HFlush(Client)
Syntax <Data file>: Character string Name of the data file used. If this name is not specified, HFlush will use the last data file used by the last HFSQL function (function starting with "H"). If this parameter corresponds to "*", HFlush will be applied to all open data files. Caution: In this case, execution of the function may take a long time.. This parameter can also correspond to the name of a group of files (or custom-folder) defined in the analysis (not available in Android and Android widget). Remarks HSecurity and HFlush HSecurity and HFlush can both be used to force a physical write operation on disk. However: - HSecurity is used to force a write operation into the data files used during each write operation. The HFSQL engine automatically performs the write operation. The data files are not closed during this write operation. This results in slower write speeds.
- HFlush forces the data file(s) to be written when it is called. The data files are closed and then re-opened during this write operation. The write operation is not slowed down.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|