Value loops - Revision history

JDamon: /* FROM and TO clause; added inclusive to FROM and exclusive to TO

2021-11-24T00:26:39Z

/* FROM and TO clause; added inclusive to FROM and exclusive to TO

← Older revision		Revision as of 00:26, 24 November 2021
Line 326:		Line 326:
	</p>		</p>
	<p>		<p>
	where the <var>FROM</var> and <var>TO</var> clauses specify the range of values to be processed. <var>FROM</var> indicates a beginning value; <var>TO</var> indicates an ending value.</p>		where the <var>FROM</var> and <var>TO</var> clauses specify the range of values to be processed. <var>FROM</var> indicates a beginning value (inclusive); <var>TO</var> indicates an ending value (exclusive).</p>

	===Intended to be used with character strings===		===Intended to be used with character strings===

ELowell: /* Syntax */

2016-10-06T22:03:14Z

Syntax

← Older revision		Revision as of 22:03, 6 October 2016
Line 62:		Line 62:
	<p>		<p>
	The complete syntax for the <var>Find All Values</var> statement in SOUL is as follows:</p>		The complete syntax for the <var>Find All Values</var> statement in SOUL is as follows:</p>
	<p class="syntax"><var class="term">label</var>:<span class="squareb">[</span>In <span class="squareb">{ </span>File <span class="term">filename</span> <span class="squareb">\|</span> Group <span class="term">groupname</span> <span class="squareb">}</span> <span class="squareb">]</span> -
	~~<span class="squareb">{</span> Find [All] Values Of <span class="squareb">\|</span> FDV <span class="squareb">}</span> <span class="term">fieldname</span> -~~
	<span class="squareb">[</span>From <span class="term">value1</span> <span class="squareb">\|</span> (<span class="term">expression1</span>)<span class="squareb">]</span> <span class="squareb">[</span>To <span class="term">value2</span> <span class="squareb">\|</span> (<span class="term">expression2</span>)<span class="squareb">]</span> -
	~~<span class="squareb">[</span>(Not) Like <span class="term">pattern</span><span class="squareb">]</span> -~~
	~~<span class="squareb">[</span>(Not) Value In <span class="term">value_set</span><span class="squareb">]</span>~~
	~~</p>~~
	<p>		<p>
	Where:</p>		Where:</p>
	<ul>		<ul>
			{{Template: Find Values Of statement syntax}}
	<li><var class="term">label</var> is necessary in order to use the result of the statement.</li>		<li><var class="term">label</var> is necessary in order to use the result of the statement.</li>

ELowell: /* Syntax */

2016-10-06T21:01:53Z

Syntax

← Older revision		Revision as of 21:01, 6 October 2016
Line 71:		Line 71:
	Where:</p>		Where:</p>
	<ul>		<ul>

			<li><var class="term">label</var> is necessary in order to use the result of the statement.</li>

	<li><var class="term">filename</var> specifies the file that has the records you want to retrieve.</li>		<li><var class="term">filename</var> specifies the file that has the records you want to retrieve.</li>

Line 86:		Line 89:

	<li>Expressions can be used for <var class="term">value1</var> and <var class="term">value2</var>, for example:		<li>Expressions can be used for <var class="term">value1</var> and <var class="term">value2</var>, for example:
	<p class="code">Find All Values Of <i>fieldname</i> ~~FROM~~ (<i>expression1</i>) TO (<i>expression2</i>)		<p class="code">Find All Values Of <i>fieldname</i> From (<i>expression1</i>) To (<i>expression2</i>)
	</p>		</p>
	<p>		<p>

ELowell at 20:54, 6 October 2016

2016-10-06T20:54:30Z

← Older revision		Revision as of 20:54, 6 October 2016
Line 55:		Line 55:
	</table>		</table>

	===~~FIND ALL VALUES~~ statement===		===Find All Values statement===
	<p>		<p>
	The <var>~~FIND ALL VALUES~~</var> statement provides an efficient value retrieval method that performs the <var>FIND</var> and <var>SORT</var> operations outside of the value loop. Each <var>~~FIND ALL VALUES~~</var> statement generates a value set header of 48 bytes.</p>		The <var>Find All Values</var> statement provides an efficient value retrieval method that performs the <var>FIND</var> and <var>SORT</var> operations outside of the value loop. Each <var>Find All Values</var> statement generates a value set header of 48 bytes.</p>

	====Syntax====		====Syntax====
	<p>		<p>
	The complete syntax for the <var>~~FIND ALL VALUES~~</var> statement in SOUL is as follows:</p>		The complete syntax for the <var>Find All Values</var> statement in SOUL is as follows:</p>
	<p class="syntax"><span class="squareb">[</span>IN <span class="squareb">{ </span>~~FILE~~ <span class="term">filename</span> <span class="squareb">\|</span> ~~GROUP~~ <span class="term">groupname</span> <span class="squareb">}</span> <span class="squareb">]</span> -		<p class="syntax"><var class="term">label</var>:<span class="squareb">[</span>In <span class="squareb">{ </span>File <span class="term">filename</span> <span class="squareb">\|</span> Group <span class="term">groupname</span> <span class="squareb">}</span> <span class="squareb">]</span> -
	<span class="squareb">{</span> ~~FIND ALL VALUES OF~~ <span class="squareb">\|</span> FDV <span class="squareb">}</span> <span class="term">fieldname</span> -		<span class="squareb">{</span> Find [All] Values Of <span class="squareb">\|</span> FDV <span class="squareb">}</span> <span class="term">fieldname</span> -
	<span class="squareb">[</span>~~FROM~~ <span class="term">value1</span><span class="squareb">]</span> <span class="squareb">[</span>TO <span class="term">value2</span><span class="squareb">]</span> <span class="squareb">[</span>(~~NOT~~) ~~LIKE~~ <span class="term">pattern</span><span class="squareb">]</span> -		<span class="squareb">[</span>From <span class="term">value1</span> <span class="squareb">\|</span> (<span class="term">expression1</span>)<span class="squareb">]</span> <span class="squareb">[</span>To <span class="term">value2</span> <span class="squareb">\|</span> (<span class="term">expression2</span>)<span class="squareb">]</span> -
	<span class="squareb">[</span>(~~NOT~~) ~~VALUE IN~~ <span class="term">value_set</span><span class="squareb">]</span>		<span class="squareb">[</span>(Not) Like <span class="term">pattern</span><span class="squareb">]</span> -
			<span class="squareb">[</span>(Not) Value In <span class="term">value_set</span><span class="squareb">]</span>
	</p>		</p>
	<p>		<p>
Line 85:		Line 86:

	<li>Expressions can be used for <var class="term">value1</var> and <var class="term">value2</var>, for example:		<li>Expressions can be used for <var class="term">value1</var> and <var class="term">value2</var>, for example:
	<p class="code">~~FIND ALL VALUES OF~~ <i>fieldname</i> FROM (<i>expression1</i>) TO (<i>expression2</i>)		<p class="code">Find All Values Of <i>fieldname</i> FROM (<i>expression1</i>) TO (<i>expression2</i>)
	</p>		</p>
	<p>		<p>
Line 493:		Line 494:
	When a FOR EACH VALUE statement appears inside another loop, the portion of the statement that finds the values is executed repeatedly, even if the set values do not change. The internal sort also is repeated for FOR EACH VALUE IN ORDER or in group context. (See [[Files, groups, and reference context]] for information about group context.)</p>		When a FOR EACH VALUE statement appears inside another loop, the portion of the statement that finds the values is executed repeatedly, even if the set values do not change. The internal sort also is repeated for FOR EACH VALUE IN ORDER or in group context. (See [[Files, groups, and reference context]] for information about group context.)</p>

	===Advantage of the ~~FIND ALL VALUES~~ statement===		===Advantage of the Find All Values statement===
	<p>		<p>
	By moving the FIND and SORT out of the loop, the cost of the inner FOR EACH VALUE loop can be reduced.</p>		By moving the FIND and SORT out of the loop, the cost of the inner FOR EACH VALUE loop can be reduced.</p>
Line 504:		Line 505:
	</p>		</p>
	<p>		<p>
	The ~~FIND ALL VALUES~~ statement is supported in remote file and scattered group contexts.</p>		The Find All Values statement is supported in remote file and scattered group contexts.</p>

	===~~FIND ALL VALUES~~ options===		===Find All Values options===
	<p>		<p>
	Like other FIND statements, a range of values can be specified for the ~~FIND ALL VALUES~~ statement by using the FROM and TO clauses. </p>		Like other FIND statements, a range of values can be specified for the Find All Values statement by using the FROM and TO clauses. </p>
	<p>		<p>
	In addition, value selection can be made based upon a pattern by using the LIKE clause.</p>		In addition, value selection can be made based upon a pattern by using the LIKE clause.</p>
Line 516:		Line 517:
	===No block end required===		===No block end required===
	<p>		<p>
	Unlike other FIND statements, the ~~FIND ALL VALUES~~ statement must not have a block end statement because ~~FIND ALL VALUES~~ does not accept multiple conditions.</p>		Unlike other FIND statements, the Find All Values statement must not have a block end statement because Find All Values does not accept multiple conditions.</p>

	===Sorting retrieved values===		===Sorting retrieved values===
	<p>		<p>
	The ~~FIND ALL VALUES~~ statement returns values in the default order. </p>		The Find All Values statement returns values in the default order. </p>
	<p>		<p>
	If a different order is required, the SORT VALUES statement must be used. For a discussion, refer to [[#SORT VALUES statement\|SORT VALUES statement]]. If a ~~FIND ALL VALUES~~ statement appears in group context, a sort is generated automatically. </p>		If a different order is required, the SORT VALUES statement must be used. For a discussion, refer to [[#SORT VALUES statement\|SORT VALUES statement]]. If a Find All Values statement appears in group context, a sort is generated automatically. </p>

	===Processing retrieved values===		===Processing retrieved values===
	<p>		<p>
	The value set resulting from a ~~FIND ALL VALUES~~ statement can be processed with this statement:</p>		The value set resulting from a Find All Values statement can be processed with this statement:</p>
	<p class="syntax">FOR EACH VALUE IN <span class="term">label</span>		<p class="syntax">FOR EACH VALUE IN <span class="term">label</span>
	</p>		</p>
Line 555:		Line 556:
	==SORT VALUES statement==		==SORT VALUES statement==
	<p>		<p>
	If you need special ordering of the value set found by the ~~FIND ALL VALUES~~ statement, use the SORT VALUES statement. </p>		If you need special ordering of the value set found by the Find All Values statement, use the SORT VALUES statement. </p>
	<p>		<p>
	The SORT VALUES statement can refer to any ~~FIND ALL VALUES~~ statement. The sorted value set can then be processed with the FOR EACH VALUE IN statement. </p>		The SORT VALUES statement can refer to any Find All Values statement. The sorted value set can then be processed with the FOR EACH VALUE IN statement. </p>
	<p>		<p>
	The ~~FIND ALL VALUES~~ statement is described in the previous section.</p>		The Find All Values statement is described in the previous section.</p>

	====Syntax====		====Syntax====

ELowell: /* Simulating a value loop for a non-FRV field */

2015-10-14T16:49:21Z

Simulating a value loop for a non-FRV field

← Older revision		Revision as of 16:49, 14 October 2015
Line 660:		Line 660:
	The following technique simulates a value loop for a field that is not multiply occurring. (See [[Processing multiply occurring fields and field groups]] for detailed information on simulating a value loop for a multiply occurring field.) </p>		The following technique simulates a value loop for a field that is not multiply occurring. (See [[Processing multiply occurring fields and field groups]] for detailed information on simulating a value loop for a multiply occurring field.) </p>
	<p>		<p>
	Assume MODEL is a non-FRV field:</p>		Assume that MODEL is a non-FRV field:</p>
	<p class="code">BEGIN		<p class="code">BEGIN
	ALL: FIND ALL RECORDS		ALL: FIND ALL RECORDS
Line 686:		Line 686:
	<p>		<p>
	If the number of values occurring on the record list is less than the number of values occurring in the entire file or group, the simulated FOR EACH VALUE loop is more efficient. This is true even for an FRV field, because the inner FIND statement is executed fewer times.</p>		If the number of values occurring on the record list is less than the number of values occurring in the entire file or group, the simulated FOR EACH VALUE loop is more efficient. This is true even for an FRV field, because the inner FIND statement is executed fewer times.</p>

	===Simulating an FRV loop on a non-ORDERED field===		===Simulating an FRV loop on a non-ORDERED field===
	<p>		<p>

ELowell: /* FRV or ORDERED field attribute required */

2015-10-14T16:48:13Z

FRV or ORDERED field attribute required

← Older revision		Revision as of 16:48, 14 October 2015
Line 141:		Line 141:
	===FRV or ORDERED field attribute required===		===FRV or ORDERED field attribute required===
	<p>		<p>
	You can only use value loops with fields that have the FRV (For Each Value) or ORDERED attribute. This is because <var class="product">Model 204</var> maintains a list of all the unique values created for a field with the FRV attribute. For a field with the ORDERED attribute, <var class="product">Model 204</var> can easily use the Ordered Index to retrieve all values created for the field. </p>		You can only use value loops with fields that have the FRV (For Each Value) or ORDERED attribute. This is because <var class="product">Model 204</var> maintains a list of all the unique values created for a field with the FRV attribute. For a field with the ORDERED attribute, <var class="product">Model 204</var> can easily use the Ordered Index to retrieve all values created for the field. </p>
	<p>		<p>
	The set of values retrieved differs depending upon the field attribute, as follows</p>		The set of values retrieved differs depending upon the field attribute, as follows:</p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 159:		Line 159:
	</table>		</table>

	To process fields ~~without~~ either the FRV or ORDERED attribute as though they did, see ~~See~~ [[#Simulating a FOR EACH VALUE loop\|Simulating a FOR EACH VALUE loop]].		To process fields that do not have either the FRV or ORDERED attribute as though they did, see [[#Simulating a FOR EACH VALUE loop\|Simulating a FOR EACH VALUE loop]].

	====Rewriting applications to take advantage of VALUE IN clause processing====		====Rewriting applications to take advantage of VALUE IN clause processing====

ELowell: /* Solution using FRV fields */

2015-10-14T16:44:02Z

Solution using FRV fields

← Older revision		Revision as of 16:44, 14 October 2015
Line 581:		Line 581:
	===Solution using FRV fields===		===Solution using FRV fields===
	<p>		<p>
	In such cases the following technique an be used if the field specified in the FOR EACH VALUE statement has the FRV attribute. This technique, however, increases processing overhead if the FRV field has many values.</p>		In such cases the following technique can be used if the field specified in the FOR EACH VALUE statement has the FRV attribute. This technique, however, increases processing overhead if the FRV field has many values.</p>
	<p class="code">BEGIN		<p class="code">BEGIN
	ALL.RECS: FIND ALL RECORDS		ALL.RECS: FIND ALL RECORDS
Line 600:		Line 600:
	END		END
	</p>		</p>

	===Solution for non-FRV fields===		===Solution for non-FRV fields===
	<p>		<p>

JAL: syntax tweak

2015-02-26T20:39:04Z

syntax tweak

Show changes

JDamon at 23:46, 25 February 2015

2015-02-25T23:46:52Z

← Older revision		Revision as of 23:46, 25 February 2015
Line 91:		Line 91:
	<li>The <var class="term">value_set</var> label represents an existing value set. NOT (optional) is the only permissible operator.		<li>The <var class="term">value_set</var> label represents an existing value set. NOT (optional) is the only permissible operator.
	<p>		<p>
	See also [[Basic SOUL statements and commands#Processing a VALUE IN clause\|Processing a VALUE IN clause]].</p>		See also [[Basic SOUL statements and commands#Processing a VALUE IN clause\|Processing a VALUE IN clause]] for other statements.</p>
	</li>		</li>

JDamon: Added FDV as an acceptable abbreviation. Removed EQ VALUE IN and NE VALUE IN clause - they don't apply to FDV.

2015-02-25T23:32:18Z

Added FDV as an acceptable abbreviation. Removed EQ VALUE IN and NE VALUE IN clause - they don't apply to FDV.

← Older revision		Revision as of 23:32, 25 February 2015
Line 60:		Line 60:
	====Syntax====		====Syntax====
	<p>		<p>
	A complete <var>FIND ALL VALUES</var> statement ~~format~~ in SOUL is as follows:</p>		The complete syntax for the <var>FIND ALL VALUES</var> statement in SOUL is as follows:</p>
	<p class="syntax"><span class="term">label</span>: FIND ALL VALUES		<p class="syntax"><span class="term">label</span>: FIND ALL VALUES or FDV

	<span class="squareb">[</span>IN <span class="squareb">{ </span>FILE <span class="term">filename</span> <span class="squareb">\|</span> GROUP <span class="term">groupname</span> <span class="squareb">}</span> <span class="squareb">]</span> -		<span class="squareb">[</span>IN <span class="squareb">{ </span>FILE <span class="term">filename</span> <span class="squareb">\|</span> GROUP <span class="term">groupname</span> <span class="squareb">}</span> <span class="squareb">]</span> -
Line 89:		Line 89:
	</li>		</li>

	<li>The <var class="term">value_set</var> label represents an existing value set. ~~Values of~~ the ~~value set in the <var>EQ VALUE IN <i>value_set</i></var> clause are treated as boolean OR, for example:</li>~~		<li>The <var class="term">value_set</var> label represents an existing value set. NOT (optional) is the only permissible operator.
	~~<p class="code"><i>field</i> = <i>value1</i> OR <i>field</i> = <i>value2</i> OR....~~
	~~</p>~~
	~~<p>~~
	~~The <var>NE VALUE IN <i>value_set</i></var> clause is likewise treated as boolean AND, for example:</p>~~
	~~<p class="code"><i>field</i> <> <i>value1</i> AND <i>field</i> <> <i>value2</i> AND...~~.
	~~</p>~~
	<p>		<p>
	See also [[Basic SOUL statements and commands#Processing a VALUE IN clause\|Processing a VALUE IN clause]].</p>		See also [[Basic SOUL statements and commands#Processing a VALUE IN clause\|Processing a VALUE IN clause]].</p>
Line 107:		Line 101:
	</li>		</li>
	</ul>		</ul>

	====Example====		====Example====
	<p> In the following example, the values of ANNIV DATE (0905, 0909, 0913, 0917, 0921, 0925) are found, counted and printed.		<p> In the following example, the values of ANNIV DATE (0905, 0909, 0913, 0917, 0921, 0925) are found, counted and printed.