Y (TQL) - Revision history

Frank@tygron.nl at 12:38, 15 May 2026

2026-05-15T12:38:07Z

← Older revision		Revision as of 12:38, 15 May 2026
Line 5:		Line 5:
	<pre>		<pre>
	[		[
	{ ~~"attributes" : { "AANTAL_HUISHOUDENS" : [ 830.0 ] },~~ "id" : 0, "name" : "De Manege" },		{ "id" : 0, "name" : "De Manege" },
	{ ~~"attributes" : { "AANTAL_HUISHOUDENS" : [ 435.0 ] },~~ "id" : 1, "name" : "De Lancaster"},		{ "id" : 1, "name" : "De Lancaster" },
	{ ~~"attributes" : { "AANTAL_HUISHOUDENS" : [ 570.0 ] },~~ "id" : 2, "name" : "De Landstreken"},		{ "id" : 2, "name" : "De Landstreken" },
	{ ~~"attributes" : { "AANTAL_HUISHOUDENS" : [ 830.0 ] },~~ "id" : 3, "name" : "De Kruidentuin"},		{ "id" : 3, "name" : "De Kruidentuin" },
	{ ~~"attributes" : { "AANTAL_HUISHOUDENS" : [ 455.0 ] },~~ "id" : 4, "name" : "Golfresidentie"}		{ "id" : 4, "name" : "Golfresidentie" }
	]		]
	</pre>		</pre>
Line 15:		Line 15:
	The TQL statement		The TQL statement
	<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,		<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,
	<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ ~~SELECT_NAME_WHERE_NEIGHBORHOOD_IS_5~~ ]</pre>		<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 a list of names, separated by comma's, for example:		Its result will be a list of names, separated by comma's, for example:
	<pre>["~~Mayfair~~"], ["~~Soho~~"], ["~~Marylebone~~"], ["~~Hyde Park~~"]</pre>		<pre>["De Manege"], ["De Lancaster"], ["De Landstreken"], ["De Kruidentuin"], ["Golfresidentie"]</pre>

	==Clause Parameters==		==Clause Parameters==

Frank@tygron.nl: /* Example */

2026-05-15T12:35:36Z

Example

@@ Line 2: / Line 2: @@
 ==Example==
 The TQL statement
 <pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,

Frank@tygron.nl at 12:14, 15 May 2026

2026-05-15T12:14:53Z

← Older revision		Revision as of 12:14, 15 May 2026
Line 21:		Line 21:


	{{TQL nav}}		{{TQL param nav}}

Frank@tygron.nl at 12:14, 15 May 2026

2026-05-15T12:14:22Z

← Older revision		Revision as of 12:14, 15 May 2026
Line 13:		Line 13:
	{{article end		{{article end
	\|seealso=		\|seealso=
	*[[XA (TQL)]]		*[[X (TQL)]]
	*[[XC (TQL)]]		*[[YA (TQL)]]
	*[[XK (TQL)]]		*[[YC (TQL)]]
	*[[Y (TQL)]]		*[[YK (TQL)]]

	}}		}}

Frank@tygron.nl at 12:14, 15 May 2026

2026-05-15T12:14:08Z

← Older revision		Revision as of 12:14, 15 May 2026
Line 4:		Line 4:
	The TQL statement		The TQL statement
	<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,		<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,
	<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_5</pre>		<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_5 ]</pre>
	Its result will be a list of names, separated by comma's, for example:		Its result will be a list of names, separated by comma's, for example:
	<pre>["Mayfair"], ["Soho"], ["Marylebone"], ["Hyde Park"]</pre>		<pre>["Mayfair"], ["Soho"], ["Marylebone"], ["Hyde Park"]</pre>

Frank@tygron.nl at 12:13, 15 May 2026

2026-05-15T12:13:49Z

← Older revision		Revision as of 12:13, 15 May 2026
Line 1:		Line 1:
	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.		Instead of specifying a clause parameter with a particular Item ID, it is possible to use the 'Y' character for its value. The result of using 'Y' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter that can be found in the project data. Internally, the resulting TQL statements are placed in an array of arrays; Similarly the result will be an array of TQL result arrays.

	~~For example, the~~ TQL statement		==Example==
			The TQL statement
	<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,		<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,
	<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_5</pre>		<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_5</pre>

Frank@tygron.nl: 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...."

2026-05-15T09:41:29Z

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...."

New page

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.

For example, the TQL statement
<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,
<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_5</pre>
Its result will be a list of names, separated by comma's, for example:
<pre>["Mayfair"], ["Soho"], ["Marylebone"], ["Hyde Park"]</pre>

==Clause Parameters==
The Y value can be used in the following TQL Clause parameters:

{{article end
|seealso=
*[[XA (TQL)]]
*[[XC (TQL)]]
*[[XK (TQL)]]
*[[Y (TQL)]]

}}

{{TQL nav}}