PC SOFT

ONLINE HELP
 WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • How the pipeline works
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Retrieves the result of the execution of a Redis command that was added by RedisPipelineAdd.
Example
RedisPipelineAdd(gRedis, "set p1 pv1")
RedisPipelineAdd(gRedis, "set p2 pv2")
RedisPipelineAdd(gRedis, "get p2")
RedisPipelineAdd(gRedis, "get p1")
 
r1 is redisResponse = RedisPipelineGet(gRedis)
r2 is redisResponse = RedisPipelineGet(gRedis)
r3 is redisResponse = RedisPipelineGet(gRedis)
r4 is redisResponse = RedisPipelineGet(gRedis)
Syntax
<Result> = RedisPipelineGet(<Connection>)
<Result>: redisResponse variable
redisResponse variable that contains the result of the Redis command.
<Connection>: redisConnection variable
Name of the redisConnection variable that corresponds to the Redis server connection.
Remarks

How the pipeline works

When all the desired commands have been added to the pipeline, the results can be retrieved with RedisPipelineGet.
To avoid retrieving the results, it is possible to use RedisPipelineReset.
If RedisPipelineReset has not been used, there must be as many calls to RedisPipelineGet as there are to RedisPipelineAdd.
Business / UI classification: Business Logic
Component: wd270big.dll
See also
Minimum version required
  • Version 24
This page is also available for…
Comments
Click [Add] to post a comment