Y (TQL): Difference between revisions
Jump to navigation
Jump to search
Created page with "Instead of specifying a clause parameter with a particular Item ID, this parameter can also be specific with 'Y'. The result of placing an Y for a clause parameter's value, is that a single TQL statement is replaced by mutliple unique TQL statements, with each one an Item ID that can be found in the project data, for that Clause Parameter. Internally, the resulting TQL statements are placed in an array of arrays and the result will be an array of TQL result arrays...." |
No edit summary |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Instead of specifying a clause parameter with a particular | Instead of specifying a clause parameter with a particular Item ID, it is possible to use the 'Y' character for its value. Using 'Y' as a clause value automatically creates multiple TQL statements—one for each Item ID associated with that parameter in the project data. Internally, the resulting TQL statements and their results are stored as arrays of arrays. | ||
==Example== | |||
<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by | Consider the following (simplified) Neighborhood data of a project: | ||
<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ | <pre> | ||
Its result will be | [ | ||
<pre>[" | { "id" : 0, "name" : "De Manege" }, | ||
{ "id" : 1, "name" : "De Lancaster" }, | |||
{ "id" : 2, "name" : "De Landstreken" }, | |||
{ "id" : 3, "name" : "De Kruidentuin" }, | |||
{ "id" : 4, "name" : "Golfresidentie" } | |||
] | |||
</pre> | |||
The TQL statement | |||
<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by commas, | |||
<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_4 ]</pre> | |||
Its result will be an array of name arrays, separated by commas, for example: | |||
<pre>["De Manege"], ["De Lancaster"], ["De Landstreken"], ["De Kruidentuin"], ["Golfresidentie"]</pre> | |||
==Clause Parameters== | ==Clause Parameters== | ||
| Line 12: | Line 24: | ||
{{article end | {{article end | ||
|seealso= | |seealso= | ||
*[[ | *[[X (TQL)]] | ||
*[[ | *[[YA (TQL)]] | ||
*[[ | *[[YC (TQL)]] | ||
*[[ | *[[YK (TQL)]] | ||
*[[ID (TQL)]] | |||
|api=*[[Api session event editor building query]] | |||
}} | }} | ||
{{TQL param nav}} | |||
{{TQL nav}} | |||
Latest revision as of 14:51, 14 July 2026
Instead of specifying a clause parameter with a particular Item ID, it is possible to use the 'Y' character for its value. Using 'Y' as a clause value automatically creates multiple TQL statements—one for each Item ID associated with that parameter in the project data. Internally, the resulting TQL statements and their results are stored as arrays of arrays.
Example
Consider the following (simplified) Neighborhood data of a project:
[
{ "id" : 0, "name" : "De Manege" },
{ "id" : 1, "name" : "De Lancaster" },
{ "id" : 2, "name" : "De Landstreken" },
{ "id" : 3, "name" : "De Kruidentuin" },
{ "id" : 4, "name" : "Golfresidentie" }
]
The TQL statement
SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y
is internally replaced with a list of TQL statement arrays, separated by commas,
[ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_4 ]
Its result will be an array of name arrays, separated by commas, for example:
["De Manege"], ["De Lancaster"], ["De Landstreken"], ["De Kruidentuin"], ["Golfresidentie"]
Clause Parameters
The Y value can be used in the following TQL Clause parameters:
See also
API Endpoints