File classes - Revision history

DCameron at 11:45, 13 April 2015

2015-04-13T11:45:36Z

← Older revision		Revision as of 11:45, 13 April 2015
Line 184:		Line 184:
	</p>		</p>

	Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record </code>		Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record</code> will result in compilation errors:
	will result in compilation errors:
	<p class="code">In File F2 For Each Record		<p class="code">In File F2 For Each Record
	Print ONLY1		Print ONLY1

DCameron at 11:44, 13 April 2015

2015-04-13T11:44:18Z

← Older revision		Revision as of 11:44, 13 April 2015
Line 184:		Line 184:
	</p>		</p>

	Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record</code>		Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record </code>
	will result in compilation errors:		will result in compilation errors:
	<p class="code">In File F2 For Each Record		<p class="code">In File F2 For Each Record
	Print ONLY1		Print ONLY1

DCameron at 11:42, 13 April 2015

2015-04-13T11:42:12Z

← Older revision		Revision as of 11:42, 13 April 2015
Line 185:		Line 185:

	Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record</code>		Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record</code>
	will result in compilation errors:		will result in compilation errors:
	<p class="code">In File F2 For Each Record		<p class="code">In File F2 For Each Record
	Print ONLY1		Print ONLY1

DCameron at 11:29, 13 April 2015

2015-04-13T11:29:27Z

← Older revision		Revision as of 11:29, 13 April 2015
Line 108:		Line 108:
	those classes, themselves, could be deep-copyable.		those classes, themselves, could be deep-copyable.

	Perhaps even more ~~important~~, this means that these objects can be passed		Perhaps even more importantly, this means that these objects can be passed
	back and forth between master and [[Daemon class\|daemon]] threads,		back and forth between master and [[Daemon class\|daemon]] threads,
	via the <var>Run</var>, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.		via the <var>Run</var>, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.

JAL at 20:37, 21 October 2013

2013-10-21T20:37:44Z

JAL at 20:48, 9 November 2012

2012-11-09T20:48:43Z

Show changes

JAL at 20:19, 9 November 2012

2012-11-09T20:19:06Z

← Older revision		Revision as of 20:19, 9 November 2012
Line 111:		Line 111:
	back and forth between master and [[Daemon class\|daemon]] threads,		back and forth between master and [[Daemon class\|daemon]] threads,
	via the <var>Run</var>, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.		via the <var>Run</var>, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.
	Among other things, this makes it easy to dynamically generate Find statements		Among other things, this makes it easy to dynamically generate <var>Find</var> statements
	that run on a daemon thread and then use the resulting found set on the master		that run on a daemon thread and then use the resulting found set on the master
	thread:		thread:
Line 342:		Line 342:
	the <var class="product">Janus SOAP ULI</var> nonsensical-field-reference protection:		the <var class="product">Janus SOAP ULI</var> nonsensical-field-reference protection:
	<ul>		<ul>
	<li>Store Record		<li><var>Store Record</var>
	<li>File Records Under		<li><var>File Records Under</var>
	<li>For Each Value		<li><var>For Each Value</var>
	<li>Find Records		<li><var>Find Records</var>
	<li>Find And Print Count		<li><var>Find And Print Count</var>
	<li>~~“~~Where~~”~~ and “Order By” clauses of For Each Record		<li>"Where" and “Order By” clauses of <var>For Each Record</var>
	<li>Find Values		<li><var>Find Values</var>
	</ul>		</ul>

Line 355:		Line 355:
	INVISIBLE in the current file:		INVISIBLE in the current file:
	<ul>		<ul>
	<li>Add		<li><var>Add</var>
	<li>Change field = oldval To newval		<li><code>Change field = oldval To newval</code>
	<li>Delete field = value		<li><code>Delete field = value</code>
	<li>Insert		<li><var>Insert</var>
	</ul>		</ul>

	===Using Is Defined and Is Visible to avoid cancellation===		===Using Is Defined and Is Visible to avoid cancellation===
	Using the same field and group definitions from [[#Request cancelled if group field reference is nonsensical for file\|"Request cancelled if group field reference is nonsensical for file"]],		Using the same field and group definitions from [[#Request cancelled if group field reference is nonsensical for file\|"Request cancelled if group field reference is nonsensical for file"]],

JAL: /* DeepCopy for file objects */

2012-11-09T19:52:42Z

DeepCopy for file objects

← Older revision		Revision as of 19:52, 9 November 2012
Line 110:		Line 110:
	Perhaps even more important, this means that these objects can be passed		Perhaps even more important, this means that these objects can be passed
	back and forth between master and [[Daemon class\|daemon]] threads,		back and forth between master and [[Daemon class\|daemon]] threads,
	via the Run, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.		via the <var>Run</var>, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.
	Among other things, this makes it easy to dynamically generate Find statements		Among other things, this makes it easy to dynamically generate Find statements
	that run on a daemon thread and then use the resulting found set on the master		that run on a daemon thread and then use the resulting found set on the master
	thread:		thread:
	<p class="code"> b		<p class="code">b

	%recs is object recordSet in file sirfiled		%recs is object recordSet in file sirfiled
	%daem is object daemon		%daem is object daemon
	%program is object stringList		%program is object stringList
	%criteria1 is string len 32		%criteria1 is string len 32
	%criteria2 is string len 32		%criteria2 is string len 32

	%criteria1 = 'rectype eq ''FILE'''		%criteria1 = 'rectype eq ''FILE'''

	%program = new		%program = new
	text to %program		text to %program
	b		b
	%recs is object recordSet in file sirfiled		%recs is object recordSet in file sirfiled
	find records to %recs		find records to %recs
	{%criteria1}		{%criteria1}
	{%criteria2}		{%criteria2}
	end find		end find
	%(daemon):returnObject(%recs)		%(daemon):returnObject(%recs)
	end		end
	end text		end text

	%daem = new		%daem = new
	%daem:open('FILE SIRFILED', default=true)		%daem:open('FILE SIRFILED', default=true)
	%daem:run('*LOWER')		%daem:run('*LOWER')
	%daem:run(%program, , %recs)		%daem:run(%program, , %recs)

	print %recs:count		print %recs:count

	end		end
	</p>		</p>

JALWiccan: 1 revision

2012-11-09T19:46:09Z

1 revision

← Older revision	Revision as of 19:46, 9 November 2012
(No difference)

JALWiccan: 1 revision

2012-11-09T19:45:42Z

1 revision

← Older revision		Revision as of 19:45, 9 November 2012
Line 110:		Line 110:
	Perhaps even more important, this means that these objects can be passed		Perhaps even more important, this means that these objects can be passed
	back and forth between master and [[Daemon class\|daemon]] threads,		back and forth between master and [[Daemon class\|daemon]] threads,
	via the Run, <var>GetInputObject</var>, <var>ReturnObject</var>, and ReturnInfoObject methods.		via the Run, <var>GetInputObject</var>, <var>ReturnObject</var>, and <var>ReturnInfoObject</var> methods.
	Among other things, this makes it easy to dynamically generate Find statements		Among other things, this makes it easy to dynamically generate Find statements
	that run on a daemon thread and then use the resulting found set on the master		that run on a daemon thread and then use the resulting found set on the master

← Older revision		Revision as of 20:37, 21 October 2013
Line 1:		Line 1:
	<!-- File classes -->		<!-- File classes -->

	One of the great strengths of <var class="product">~~User Language~~</var> is the tight integration of the		One of the great strengths of <var class="product">SOUL</var> is the tight integration of the
	'''database Manipulation Language''', often abbreviated DML,		'''database Manipulation Language''', often abbreviated DML,
	with the programming language.		with the programming language.
	That is, statements like Find, <var>For Each Record</var>, and <var>For Each Occurrence</var>		That is, statements like <var>Find</var>, <var>For Each Record</var>, and <var>For Each Occurrence</var>
	can be easily embedded in <var class="product">~~User Language~~</var> procedure code.		can be easily embedded in <var class="product">SOUL</var> procedure code.
	Embedding some of these statements in methods, however, can be problematic,		Embedding some of these statements in methods, however, can be problematic,
	and it would be very useful to have object-oriented versions of some standard <var class="product">~~User Language~~</var>		and it would be very useful to have object-oriented versions of some standard <var class="product">SOUL</var>
	file-oriented facilities.		file-oriented facilities.

Line 28:		Line 28:
	for an instance of a class.		for an instance of a class.

	~~The~~ <var class="product">~~[[Janus SOAP User Language Interface\|Janus SOAP ULI]]~~</var> provides these capabilities with record set, record,		<var class="product">SOUL</var> provides these capabilities with record set, record,
	and sorted record set objects.		and sorted record set objects.
	The classes, associated with <var class="product">Model 204</var> file structures, are called		The classes, associated with <var class="product">Model 204</var> file structures, are called
Line 65:		Line 65:
	<tr><th>fileClassName</th>		<tr><th>fileClassName</th>
	<td>The name of a file class.		<td>The name of a file class.
	~~<var class="product">Sirius Mods</var> supports~~ the <var>Recordset</var>, <var>Record</var>, <var>RecordsetCursor</var>, and <var>SortedRecordset</var> classes.</td></tr>		Options are the <var>Recordset</var>, <var>Record</var>, <var>RecordsetCursor</var>, and <var>SortedRecordset</var> classes.</td></tr>

	<tr><th>fgname</th>		<tr><th>fgname</th>
Line 105:		Line 105:
	==DeepCopy for file objects==		==DeepCopy for file objects==
	The <var>Record</var>, <var>Recordset</var>, and <var>SortedRecordset</var> objects are deep-copyable.		The <var>Record</var>, <var>Recordset</var>, and <var>SortedRecordset</var> objects are deep-copyable.
	This means that these objects can be contained inside <var class="product">~~User Language~~</var> classes and		This means that these objects can be contained inside <var class="product">SOUL</var> classes and
	those classes, themselves, could be deep-copyable.		those classes, themselves, could be deep-copyable.

Line 147:		Line 147:

	==Request cancelled if group field reference is nonsensical for file==		==Request cancelled if group field reference is nonsensical for file==
	One of the benefits of the <var class="product">~~Janus SOAP ULI~~</var> File classes is easier migration		One of the benefits of the <var class="product">SOUL</var> File classes is easier migration
	between file-context and group-context <var class="product">~~User Language~~</var>.		between file-context and group-context <var class="product">SOUL</var>.
	In most cases, this is provided by allowing the same <var class="product">~~User Language~~</var> code to		In most cases, this is provided by allowing the same <var class="product">SOUL</var> code to
	operate whether in file or group context.		operate whether in file or group context.

Line 163:		Line 163:
	references to the value of that field, or nonsensical updates to that field.		references to the value of that field, or nonsensical updates to that field.

	With version 7.0 of <var class="product">Janus SOAP ULI</var>~~, your~~ applications are		<!-- With version 7.0 of <var class="product">Janus SOAP ULI</var> -->
	protected against nonsense field references when done in the context		Your applications are protected against nonsense field references when done in the context
	of <var class="product">~~Janus SOAP ULI~~</var> File objects.		of <var class="product">SOUL</var> File objects.
	The '''general''' (but not exact — see [[#Exact rules of group field cancellation\|"Exact rules of group field cancellation"]])		The '''general''' (but not exact — see [[#Exact rules of group field cancellation\|"Exact rules of group field cancellation"]])
	guideline is that the request is cancelled if '''both''' these conditions exist:		guideline is that the request is cancelled if '''both''' these conditions exist:
Line 184:		Line 184:
	</p>		</p>

	Each of the <var class="product">~~User Language~~</var> statements within the following <code>For Each Record</code>		Each of the <var class="product">SOUL</var> statements within the following <code>For Each Record</code>
	will result in compilation errors:		will result in compilation errors:
	<p class="code">In File F2 For Each Record		<p class="code">In File F2 For Each Record
Line 200:		Line 200:
	<li>You cannot delete, by occurrence, a field that is <var>INVISIBLE</var> (<code>Delete VIS1</code>).		<li>You cannot delete, by occurrence, a field that is <var>INVISIBLE</var> (<code>Delete VIS1</code>).
	</ul>		</ul>
	If you convert this application (which does not use the <var class="product">~~Janus SOAP ULI~~</var> File		If you convert this application (which does not use the <var class="product">SOUL</var> File
	classes) to use a group, it compiles and evaluates without any complaint:		classes) to use a group, it compiles and evaluates without any complaint:
	<p class="code">In Group G For Each Record		<p class="code">In Group G For Each Record
Line 210:		Line 210:
	</p>		</p>
	However, when the current file in the <code>For Each Record</code>		However, when the current file in the <code>For Each Record</code>
	loop is <code>F2</code>, the following occur, and this '''may be an application		loop is <code>F2</code>, the following occur, and this '''may be an application error''':
	error''':
	<ul>		<ul>
	<li>The value (<code>Print ONLY1</code>)		<li>The value (<code>Print ONLY1</code>)
Line 223:		Line 222:
	</ul>		</ul>

	~~The~~ <var class="product">~~Janus SOAP ULI~~</var> takes a more conservative approach to handling fields that		<var class="product">SOUL</var> takes a more conservative approach to handling fields that
	are undefined or <var>INVISIBLE</var> in some members of a group, when the field references are in records		are undefined or <var>INVISIBLE</var> in some members of a group, when the field references are in records
	that are bound to an object in one of the File classes.		that are bound to an object in one of the File classes.
Line 311:		Line 310:
	'''Then''' the request will be cancelled.		'''Then''' the request will be cancelled.

	'''Note:'''		<p class="note">'''Note:'''
	In addition to the list of statements above (<var>CTO</var>, <var>FEO</var>, etc.)		In addition to the list of statements above (<var>CTO</var>, <var>FEO</var>, etc.)
	which do not cause request cancellation, a few updating		which do not cause request cancellation, a few updating
	statements are shown in the next list, and updating		statements are shown in the next list, and updating
	statements for <var>INVISIBLE</var> fields are shown in the list after that,		statements for <var>INVISIBLE</var> fields are shown in the list after that,
	which do not cause request cancellation.		which do not cause request cancellation. </p>

	==Other statements that do not cancel request==		==Other statements that do not cancel request==
Line 322:		Line 321:
	due to nonsensical field references is that a record referenced in a group context is		due to nonsensical field references is that a record referenced in a group context is
	bound to an object of one of the File classes, and that a field is referenced using that record.		bound to an object of one of the File classes, and that a field is referenced using that record.
	The following <var class="product">~~User Language~~</var> statements refer to fields but		The following <var class="product">SOUL</var> statements refer to fields but
	are not in a record context, so they are not subject to		are not in a record context, so they are not subject to
	the <var class="product">~~Janus SOAP ULI~~</var> nonsensical-field-reference protection:		the <var class="product">SOUL</var> nonsensical-field-reference protection:
	<ul>		<ul>
	<li><var>Store Record</var>		<li><var>Store Record</var>
Line 346:		Line 345:

	===Using Is Defined and Is Visible to avoid cancellation===		===Using Is Defined and Is Visible to avoid cancellation===
	Using the same field and group definitions from [[#Request cancelled if group field reference is nonsensical for file\|"Request cancelled if group field reference is nonsensical for file"]], here is a <var class="product">~~User Language~~</var> request that skips nonsensical field references:		Using the same field and group definitions from [[#Request cancelled if group field reference is nonsensical for file\|"Request cancelled if group field reference is nonsensical for file"]], here is a <var class="product">SOUL</var> request that skips nonsensical field references:
	<p class="code">Begin		<p class="code">Begin
	%rs Object Recordset In Group G		%rs Object Recordset In Group G
Line 363:		Line 362:
	End		End
	</p>		</p>
	Note that this is not the same result as the second <var class="product">~~User Language~~</var> example		Note that this is not the same result as the second <var class="product">SOUL</var> example
	(<code>In Group G For Each Record</code>) in		(<code>In Group G For Each Record</code>) in
	[[#Request cancelled if group field reference is nonsensical for file\|"Request cancelled if group field reference is nonsensical for file"]].		[[#Request cancelled if group field reference is nonsensical for file\|"Request cancelled if group field reference is nonsensical for file"]].