|
|
|
|
|
|
|
|
|
|
<ParallelTask variable>.Execute (Función) Triggers the execution of a parallel task.
t1 is ParallelTask
t1.Procedure = Procedure3
t2 is ParallelTask = t1.Execute()
Sintaxis
Ejecutar una tarea paralela descrita de antemano (variable ParallelTask) Ocultar los detalles
<Result> = <Task>.Execute()
<Result>: La variable ParallelTask ParallelTask variable corresponding to the task run. <Task>: La variable ParallelTask Name of the ParallelTask variable corresponding to the task to run. Warning: If the task is already running or has already been executed, a WLanguage error will be triggered. Observaciones - 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, ...).
- positions, filters, etc. defined on 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 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.
Esta página también está disponible para…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|