|
|
|
|
|
<Description of ParallelTask>.Execute (Función) Triggers the execution of a parallel task.
t3bis is Description of ParallelTask
t3bis.Procedure = Procedure3bis
t3bis.Parameter[1] = Today()
t3bis.Parameter[2] = TimeSys()
t3bis.Execute()
Sintaxis
Ejecutar una tarea paralela identificada por su descripción (variable Description of ParallelTask) Ocultar los detalles
<Result> = ParallelTaskExecute(<Task description>)
<Result>: La variable ParallelTask ParallelTask variable corresponding to the task run. <Task description>: Descripción de la variable ParallelTask Name of the Description of ParallelTask variable that describes the task to be executed. Observaciones - The task is saved in the queue of tasks to run.
- <Description of ParallelTask>.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…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|