|
|
|
|
<ParallelTask variable>.Execute (Function) In french: <Variable TâcheParallèle>.Exécute Triggers the execution of a parallel task.
// Use the syntax 2 t1 is ParallelTask t1.Procédure = Procedure3 t2 is ParallelTask = t1.Exécute() Syntax
Running a parallel task described beforehand (ParallelTask variable) Hide the details
<Result> = <Task>.Execute()
<Result>: ParallelTask variable ParallelTask variable corresponding to the task run. <Task>: ParallelTask variable Name of the ParallelTask variable corresponding to the task to run. Caution: A WLanguage error occurs if the task is currently run or if the task was already run. Remarks - The task is saved in the queue of tasks to run.
- <ParallelTask variable>.Execute is not a blocking function and does not wait for task to be completed.
- Comparison between the different types of copy for the HFSQL context:
| | | Type of copy | Benefits | Drawbacks |
---|
Full copy | Copies: - the extensive connection parameters (connections, physical paths, ...).
- the positions, the filters, ... defined on the data files.
- the queries.
| Memory consumption (on the client and on the server). | Light copy | Copies the extensive connection parameters (connections, physical paths, ...). No memory consumption on the server. | The records and the current filters are not copied. Therefore, the records must be repositioned by HReadSeek for example. No copy of queries. Memory consumption on the Client computer | Delayed copy | No memory consumption (on the client and on the server). | Risk: If the extended connection parameters are modified, the last modification will be taken into account. The records and the current filters are not copied. Therefore, the records must be repositioned by HReadSeek for example. No copy of queries. |
In most cases, the delayed copy is recommended provided that you don't change the connection parameters and that you perform the necessary calls to HReadSeek.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|