Reserved words and characters - Revision history

JAL at 15:57, 18 August 2014

2014-08-18T15:57:07Z

← Older revision		Revision as of 15:57, 18 August 2014
Line 123:		Line 123:
	<td>)</td>		<td>)</td>
	<td>*</td>		<td>*</td>
	<td>^</td> <!-- char is undecipherable, missing/incorrect for years -->		<td>^</td> <!-- char was undecipherable, missing/incorrect for years -->
	</tr>		</tr>
	<tr>		<tr>
Line 133:		Line 133:
	<td>...</td>		<td>...</td>
	<td>:</td>		<td>:</td>
	<td>% </td>		<td>% </td>
	</tr>		</tr>
	</table>		</table>
Line 140:		Line 140:

	====How to refer to a field name containing reserved words or characters====		====How to refer to a field name containing reserved words or characters====
	<p>As in ~~[[#Rules for reserved~~ words and ~~characters]] and [[#Rules for reserved words~~ and characters]], if a field name does contain a reserved word or character, you must enclose it in single quotes when referencing it in a request. For example, the following FIND statement references a field named NOR SLS:</p>		<p>
			As in the "Reserved words and operators" and "Reserved characters" tables above, if a field name does contain a reserved word or character, you must enclose it in single quotes when referencing it in a request. For example, the following <var>FIND</var> statement references a field named <code>NOR SLS</code>:</p>
	<p class="code">FIND ALL RECORDS FOR WHICH 'NOR SLS' > 0		<p class="code">FIND ALL RECORDS FOR WHICH 'NOR SLS' > 0
	</p>		</p>

Tbullock: Restore the old NOT sign ^. I think that is what it was according to the ancient printed 4.1 manual. That book had a semicolon and an asterisk too though.

2014-08-15T22:45:57Z

Restore the old NOT sign ^. I think that is what it was according to the ancient printed 4.1 manual. That book had a semicolon and an asterisk too though.

← Older revision		Revision as of 22:45, 15 August 2014
Line 123:		Line 123:
	<td>)</td>		<td>)</td>
	<td>*</td>		<td>*</td>
	<td></td> <!-- char is undecipherable, missing/incorrect for years -->		<td>^</td> <!-- char is undecipherable, missing/incorrect for years -->
	</tr>		</tr>
	<tr>		<tr>

JAL at 21:54, 14 April 2014

2014-04-14T21:54:15Z

← Older revision		Revision as of 21:54, 14 April 2014
Line 1:		Line 1:
	===Rules for reserved words and characters===		===Rules for reserved words and characters===
	<p>A number of words and characters have special meaning to <var class="product">Model 204</var> and either cannot be used as part of field names or values or can only be used as part of a quoted string.</p>		<p>
	<p>The rules for <var class="product">Model 204</var> reserved words and characters are as follows: </p>		A number of words and characters have special meaning to <var class="product">Model 204</var> and either cannot be used as part of field names or values or can only be used as part of a quoted string.</p>
			<p>
			The rules for <var class="product">Model 204</var> reserved words and characters are as follows: </p>
	<ul>		<ul>
	<li>Any word or character, including the space character, can be used as part of a field name, except the following:~~</li>~~		<li>Any word or character, including the space character, can be used as part of a field name, except the following:
	<table>		<table>
	<tr>		<tr>
	<td>??</td>		<td>??</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>?$</td>		<td>?$</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>?&</td>		<td>?&</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>@ (as delete character)</td>		<td>@ (as delete character)</td>
	</tr>		</tr>

	<tr>		<tr>
	<td># (as flush character)</td>		<td># (as flush character)</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>; </td>		<td>; </td>
	</tr>		</tr>
	</table>		</table></li>
	</ul>		</ul>

	<p class="note"><b>Note:</b> The delete (@) and flush (#) characters used at an installation are controlled by the ERASE and ~~FLUSH parameters (described in the Rocket~~ <var ~~class="product"~~>~~Model 204~~</var> ~~Parameter and Command Reference Manual)~~. If different symbols are chosen, the restriction on using these characters in field names applies to the new symbols.</p>		<p class="note"><b>Note:</b> The delete (@) and flush (#) characters used at an installation are controlled by the <var>[[ERASE parameter\|ERASE]]</var> and <var>[[FLUSH parameter\|FLUSH]]</var> parameters. If different symbols are chosen, the restriction on using these characters in field names applies to the new symbols.</p>
	<ul>		<ul>
	<li>The following list of reserved words or operators can be part of a string-without-quotes as long as they are not surrounded by spaces (ANDIRON is acceptable while AND IRON is not). They can be part of a quoted string as long as they do not stand alone ('A OR B' is acceptable while 'OR' is not). Although field names and values can contain reserved words, requests which reference those fields might not compile, or might produce unexpected results. ~~</li>~~		<li>The following list of reserved words or operators can be part of a string-without-quotes as long as they are not surrounded by spaces (ANDIRON is acceptable while AND IRON is not). They can be part of a quoted string as long as they do not stand alone ('A OR B' is acceptable while 'OR' is not). Although field names and values can contain reserved words, requests which reference those fields might not compile, or might produce unexpected results.

	<table style="table-layout: fixed;">		<table style="table-layout: fixed;">
Line 98:		Line 105:
	</li>		</li>

	<li>If any of the following reserved characters is embedded in a field name, the character must be part of a quoted string. When creating field names, Rocket Software recommends avoiding the following characters: ~~</li>~~		<li>If any of the following reserved characters is embedded in a field name, the character must be part of a quoted string. When creating field names, Rocket Software recommends avoiding the following characters:

	<table>		<table>
Line 136:		Line 143:
	<p class="code">FIND ALL RECORDS FOR WHICH 'NOR SLS' > 0		<p class="code">FIND ALL RECORDS FOR WHICH 'NOR SLS' > 0
	</p>		</p>
	<p>The following DISPLAY command references a procedure called %SAVINGS:</p>		<p>
			The following <var>DISPLAY</var> command references a procedure called <code>%SAVINGS</code>:</p>
	<p class="code">DISPLAY PROCEDURE '%SAVINGS'		<p class="code">DISPLAY PROCEDURE '%SAVINGS'
	</p>		</p>

	[[Category:SOUL]]		[[Category:SOUL]]

Admin at 16:27, 2 January 2014

2014-01-02T16:27:55Z

← Older revision		Revision as of 16:27, 2 January 2014
Line 100:		Line 100:
	<li>If any of the following reserved characters is embedded in a field name, the character must be part of a quoted string. When creating field names, Rocket Software recommends avoiding the following characters: </li>		<li>If any of the following reserved characters is embedded in a field name, the character must be part of a quoted string. When creating field names, Rocket Software recommends avoiding the following characters: </li>

	~~/* note; one char is undecipherable, missing/incorrect for years */~~
	<table>		<table>
	<caption>Reserved characters</caption>		<caption>Reserved characters</caption>
Line 117:		Line 116:
	<td>)</td>		<td>)</td>
	<td>*</td>		<td>*</td>
	<td></td>		<td></td> <!-- char is undecipherable, missing/incorrect for years -->
	</tr>		</tr>
	<tr>		<tr>

Admin at 16:24, 2 January 2014

2014-01-02T16:24:53Z

← Older revision		Revision as of 16:24, 2 January 2014
Line 99:		Line 99:

	<li>If any of the following reserved characters is embedded in a field name, the character must be part of a quoted string. When creating field names, Rocket Software recommends avoiding the following characters: </li>		<li>If any of the following reserved characters is embedded in a field name, the character must be part of a quoted string. When creating field names, Rocket Software recommends avoiding the following characters: </li>

			/* note; one char is undecipherable, missing/incorrect for years */
	<table>		<table>
	<caption>Reserved characters</caption>		<caption>Reserved characters</caption>
Line 111:		Line 113:
	<td>- (minus sign/hyphen)</td>		<td>- (minus sign/hyphen)</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>)</td>		<td>)</td>
	<td>*</td>		<td>*</td>
	<td></td> ~~/* undecipherable, missing/incorrect for years */~~		<td></td>
	</tr>		</tr>
	<tr>		<tr>

JAL: /* Rules for reserved words and characters */

2014-01-02T16:00:42Z

Rules for reserved words and characters

← Older revision		Revision as of 16:00, 2 January 2014
Line 29:		Line 29:
	<ul>		<ul>
	<li>The following list of reserved words or operators can be part of a string-without-quotes as long as they are not surrounded by spaces (ANDIRON is acceptable while AND IRON is not). They can be part of a quoted string as long as they do not stand alone ('A OR B' is acceptable while 'OR' is not). Although field names and values can contain reserved words, requests which reference those fields might not compile, or might produce unexpected results. </li>		<li>The following list of reserved words or operators can be part of a string-without-quotes as long as they are not surrounded by spaces (ANDIRON is acceptable while AND IRON is not). They can be part of a quoted string as long as they do not stand alone ('A OR B' is acceptable while 'OR' is not). Although field names and values can contain reserved words, requests which reference those fields might not compile, or might produce unexpected results. </li>

	<table style="table-layout: fixed;">		<table style="table-layout: fixed;">
	<caption>Reserved words and operators</caption>		<caption>Reserved words and operators</caption>
	<tr>		<tr>
	<td style="width: 5em">AFTER</td>		<td style="width: 5em">AFTER</td>
	<td style="width: 5em">~~COUNT~~</td>		<td style="width: 5em">EACH</td>
	<td style="width: ~~7em~~">~~LIKE~~</td>		<td style="width: 8em">NOT</td>
	<td style="width: 5em">~~ORIF~~</td>		<td style="width: 5em">TAB</td>
	<td style="width: 5em">~~VALUES</td>~~		<td style="width: 5em">EQ</td>
	~~<td style="width: 5em">LT~~</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>ALL</td>		<td>ALL</td>
	<td>~~EACH~~</td>		<td>EDIT</td>
	<td>~~NOR~~</td>		<td>OCC</td>
	<td>~~RECORD~~</td>		<td>THEN</td>
	<td>~~WHERE </td>~~		<td>GE</td>
	~~<td>NE~~</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>AND</td>		<td>AND</td>
	<td>~~EDIT~~</td>		<td>END</td>
	<td>~~NOT~~</td>		<td>OCCURRENCE</td>
	<td>~~RECORDS~~</td>		<td>TO</td>
	<td>~~WITH</td>~~		<td>GT</td>
	~~<td> ~~</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>ANDIF</td>		<td>ANDIF</td>
	<td>~~END~~</td>		<td>FROM</td>
	<td>~~OCC~~</td>		<td>ON</td>
	<td>~~TAB~~</td>		<td>VALUE</td>
	<td>EQ</td>		<td>LE</td>
	~~<td> </td>~~
	</tr>		</tr>
	<tr>		<tr>
	<td>AT</td>		<td>AT</td>
	<td>~~FROM~~</td>		<td>IN</td>
	<td>~~OCCURRENCE~~</td>		<td>OR</td>
	<td>~~THEN~~</td>		<td>VALUES</td>
	<td>~~GE</td>~~		<td>LT</td>
	~~<td> ~~</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>BEFORE</td>		<td>BEFORE</td>
	<td>IN</td>		<td>IS</td>
	<td>ON</td>		<td>ORIF</td>
	<td>TO</td>		<td>WHERE </td>
	<td>~~GT</td>~~		<td>NE</td>
	~~<td> ~~</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>BY</td>		<td>BY</td>
	<td>IS</td>		<td>LIKE</td>
	<td>OR</td>		<td>RECORD</td>
	<td>~~VALUE~~</td>		<td>WITH</td>
	<td>LE</td>		<td></td>
	<td>~~ ~~</td>		</tr>

			<tr>
			<td>COUNT</td>
			<td>NOR</td>
			<td>RECORDS</td>
			<td></td>
			<td></td>
	</tr>		</tr>
	</table>		</table>

JAL at 15:38, 2 January 2014

2014-01-02T15:38:15Z

← Older revision		Revision as of 15:38, 2 January 2014
Line 32:		Line 32:
	<caption>Reserved words and operators</caption>		<caption>Reserved words and operators</caption>
	<tr>		<tr>
	<td style="width: ~~6em~~">AFTER</td>		<td style="width: 5em">AFTER</td>
	<td style="width: ~~6em~~">COUNT</td>		<td style="width: 5em">COUNT</td>
	<td style="width: ~~6em~~">LIKE</td>		<td style="width: 7em">LIKE</td>
	<td style="width: ~~6em~~">ORIF</td>		<td style="width: 5em">ORIF</td>
	<td style="width: ~~6em~~">VALUES</td>		<td style="width: 5em">VALUES</td>
	<td style="width: ~~6em~~">LT</td>		<td style="width: 5em">LT</td>
	</tr>		</tr>
	<tr>		<tr>

JAL at 15:35, 2 January 2014

2014-01-02T15:35:33Z

← Older revision		Revision as of 15:35, 2 January 2014
Line 32:		Line 32:
	<caption>Reserved words and operators</caption>		<caption>Reserved words and operators</caption>
	<tr>		<tr>
	<td style="width: ~~5em~~">AFTER</td>		<td style="width: 6em">AFTER</td>
	<td style="width: ~~5em~~">COUNT</td>		<td style="width: 6em">COUNT</td>
	<td style="width: ~~5em~~">LIKE</td>		<td style="width: 6em">LIKE</td>
	<td style="width: ~~5em~~">ORIF</td>		<td style="width: 6em">ORIF</td>
	<td style="width: ~~5em~~">VALUES</td>		<td style="width: 6em">VALUES</td>
	<td style="width: ~~5em~~">LT</td>		<td style="width: 6em">LT</td>
	</tr>		</tr>
	<tr>		<tr>

JAL at 03:07, 2 January 2014

2014-01-02T03:07:30Z

← Older revision		Revision as of 03:07, 2 January 2014
Line 123:		Line 123:

	====How to refer to a field name containing reserved words or characters====		====How to refer to a field name containing reserved words or characters====
	<p>As in [[#~~Rules for reserved words and characters\|~~Rules for reserved words and characters]] and [[#~~Rules for reserved words and characters\|~~Rules for reserved words and characters]], if a field name does contain a reserved word or character, you must enclose it in single quotes when referencing it in a request. For example, the following FIND statement references a field named NOR SLS:</p>		<p>As in [[#Rules for reserved words and characters]] and [[#Rules for reserved words and characters]], if a field name does contain a reserved word or character, you must enclose it in single quotes when referencing it in a request. For example, the following FIND statement references a field named NOR SLS:</p>
	<p class="code">FIND ALL RECORDS FOR WHICH 'NOR SLS' > 0		<p class="code">FIND ALL RECORDS FOR WHICH 'NOR SLS' > 0
	</p>		</p>

JAL at 03:04, 2 January 2014

2014-01-02T03:04:38Z

← Older revision		Revision as of 03:04, 2 January 2014
Line 106:		Line 106:
	<td>)</td>		<td>)</td>
	<td>*</td>		<td>*</td>
	<td></td>		<td></td> /* undecipherable, missing/incorrect for years */
	</tr>		</tr>
	<tr>		<tr>