LockStrength enumeration - Revision history

JAL: add "See also" section

2018-04-23T16:34:24Z

add "See also" section

← Older revision		Revision as of 16:34, 23 April 2018
Line 22:		Line 22:

	<p class="note">'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|Common enumeration methods]].</p>		<p class="note">'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|Common enumeration methods]].</p>

			==See also==
			<ul>
			<li>[[Lists of classes and methods#Enumerations\|List of system enumerations]] </li>
			<li>[[Object oriented programming in SOUL]] </li>
			</ul>

JAL at 20:31, 30 June 2014

2014-06-30T20:31:59Z

← Older revision		Revision as of 20:31, 30 June 2014
Line 5:		Line 5:
	<table>		<table>
	<tr>		<tr>
	<th>None</th>		<th><var>None</var></th>
	<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for <var>Recordsets</var>.</td>		<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for <var>Recordsets</var>.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>Share</th>		<th><var>Share</var></th>
	<td>Object is locked in share mode.<br/>This level allows other users to hold a <var>Share</var> lock, but not an <var>Exclusive</var> lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for <var>Recordsets</var>.</td>		<td>Object is locked in share mode.<br/>This level allows other users to hold a <var>Share</var> lock, but not an <var>Exclusive</var> lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for <var>Recordsets</var>.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>Exclusive</th>		<th><var>Exclusive</var></th>
	<td>Object is locked in exclusive mode.<br/>This level prohibits others from holding either an <var>Exclusive</var> lock or a <var>Share</var> lock. It is generally used for update. <var>Find And Reserve</var> statements acquire this type of record lock.</td>		<td>Object is locked in exclusive mode.<br/>This level prohibits others from holding either an <var>Exclusive</var> lock or a <var>Share</var> lock. It is generally used for update. <var>Find And Reserve</var> statements acquire this type of record lock.</td>
	</tr>		</tr>
Line 19:		Line 21:
	Typically, exclusive locks are used when there is an intent to update one or more of the records referenced by an object. A share lock is used to ensure a consistent view of records associated with an object, as such a lock prevents any other user from updating those records since an update requires an exclusive lock on a record. Unlocked (<var>LockStrength None</var>) records can be used where mechanisms other than locking are used to protect the integrity of field references, or in cases where an object is used to reference one or more records but the records are temporarily locked in share mode when they are actually referenced. [[LoopLockStrength (Record property)]] and [[LoopLockStrength (Recordset property)]] facilitate this kind of processing.		Typically, exclusive locks are used when there is an intent to update one or more of the records referenced by an object. A share lock is used to ensure a consistent view of records associated with an object, as such a lock prevents any other user from updating those records since an update requires an exclusive lock on a record. Unlocked (<var>LockStrength None</var>) records can be used where mechanisms other than locking are used to protect the integrity of field references, or in cases where an object is used to reference one or more records but the records are temporarily locked in share mode when they are actually referenced. [[LoopLockStrength (Record property)]] and [[LoopLockStrength (Recordset property)]] facilitate this kind of processing.

	'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|"Common enumeration methods"]].		<p class="note">'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|Common enumeration methods]].</p>

JAL at 16:20, 27 November 2012

2012-11-27T16:20:05Z

← Older revision		Revision as of 16:20, 27 November 2012
Line 1:		Line 1:
	<!-- LockingStrength enumeration -->		<!-- LockingStrength enumeration -->
	This enumeration is used to indicate the strength of a lock, and is often used in controlling locking for <var>[[Record_class\|Record]]</var> and <var>[[Recordset_class\|Recordset]]</var> objects. When an object referencing one or more records is instantiated, the referenced records are locked with a particular lock strength, either implicitly as with the <var>Find All Records</var> and <var>Find And Reserve</var> statements or explicitly as with the [[New (Record constructor)]] and [[New (Recordset constructor)]] methods.		This [[Enumerations\|enumeration]] is used to indicate the strength of a lock, and is often used in controlling locking for <var>[[Record_class\|Record]]</var> and <var>[[Recordset_class\|Recordset]]</var> objects. When an object referencing one or more records is instantiated, the referenced records are locked with a particular lock strength, either implicitly as with the <var>Find All Records</var> and <var>Find And Reserve</var> statements or explicitly as with the [[New (Record constructor)]] and [[New (Recordset constructor)]] methods.

	These are the valid values of this ~~[[Enumerations\|~~enumeration]], which correspond to standard <var class="product">Model 204</var> record-locking levels:		These are the valid values of this enumeration, which correspond to standard <var class="product">Model 204</var> record-locking levels:
	<table>		<table>
	<tr>		<tr>
	<th>None</th>		<th>None</th>
	<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for Recordsets.</td>		<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for <var>Recordsets</var>.</td>
	</tr>		</tr>
	<tr>		<tr>
	<th>Share</th>		<th>Share</th>
	<td>Object is locked in share mode.<br/>This level allows other users to hold a Share lock, but not an Exclusive lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for Recordsets.</td>		<td>Object is locked in share mode.<br/>This level allows other users to hold a <var>Share</var> lock, but not an <var>Exclusive</var> lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for <var>Recordsets</var>.</td>
	</tr>		</tr>
	<tr>		<tr>
Line 17:		Line 17:
	</tr>		</tr>
	</table>		</table>
	Typically, exclusive locks are used when there is an intent to update one or more of the records referenced by an object. A share lock is used to ensure a consistent view of records associated with an object, as such a lock prevents any other user from updating those records since an update requires an exclusive lock on a record. Unlocked (LockStrength None) records can be used where mechanisms other than locking are used to protect the integrity of field references, or in cases where an object is used to reference one or more records but the records are temporarily locked in share mode when they are actually referenced. ~~The~~ [[~~LoopLockStrength_~~(~~Record_property~~)~~\|Record~~]] and [[~~LoopLockStrength_~~(~~Recordset_property~~)~~\|Recordset~~]] ~~class LoopLockStrength properties~~ facilitate this kind of processing.		Typically, exclusive locks are used when there is an intent to update one or more of the records referenced by an object. A share lock is used to ensure a consistent view of records associated with an object, as such a lock prevents any other user from updating those records since an update requires an exclusive lock on a record. Unlocked (<var>LockStrength None</var>) records can be used where mechanisms other than locking are used to protect the integrity of field references, or in cases where an object is used to reference one or more records but the records are temporarily locked in share mode when they are actually referenced. [[LoopLockStrength (Record property)]] and [[LoopLockStrength (Recordset property)]] facilitate this kind of processing.

	'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|"Common enumeration methods"]].		'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|"Common enumeration methods"]].

JAL at 00:00, 27 November 2012

2012-11-27T00:00:43Z

← Older revision		Revision as of 00:00, 27 November 2012
Line 1:		Line 1:
	<!-- LockingStrength enumeration -->		<!-- LockingStrength enumeration -->
	This enumeration is used to indicate the strength of a lock, and is often used in controlling locking for [[Record_class\|~~Records~~]] and [[Recordset_class\|~~Recordsets~~]]. When an object referencing one or more records is instantiated, the referenced records are locked with a particular lock strength, either implicitly as with the <var>Find All Records</var> and <var>Find And Reserve</var> statements or explicitly as with the [[~~New_~~(~~Record_constructor~~)~~\|Record~~]] and [[~~New_~~(~~Recordset_constructor~~)~~\|Recordset~~]] ~~class constructors~~.		This enumeration is used to indicate the strength of a lock, and is often used in controlling locking for <var>[[Record_class\|Record]]</var> and <var>[[Recordset_class\|Recordset]]</var> objects. When an object referencing one or more records is instantiated, the referenced records are locked with a particular lock strength, either implicitly as with the <var>Find All Records</var> and <var>Find And Reserve</var> statements or explicitly as with the [[New (Record constructor)]] and [[New (Recordset constructor)]] methods.

	These are the valid values of this [[Enumerations\|enumeration]], which correspond to standard <var class="product">Model 204</var> record-locking levels:		These are the valid values of this [[Enumerations\|enumeration]], which correspond to standard <var class="product">Model 204</var> record-locking levels:

Alex at 13:44, 30 August 2012

2012-08-30T13:44:00Z

← Older revision		Revision as of 13:44, 30 August 2012
Line 5:		Line 5:
	<table>		<table>
	<tr>		<tr>
	<td>None</td>		<th>None</th>
	<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for Recordsets.</td>		<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for Recordsets.</td>
	</tr>		</tr>
	<tr>		<tr>
	<td>Share</td>		<th>Share</th>
	<td>Object is locked in share mode.<br/>This level allows other users to hold a Share lock, but not an Exclusive lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for Recordsets.</td>		<td>Object is locked in share mode.<br/>This level allows other users to hold a Share lock, but not an Exclusive lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for Recordsets.</td>
	</tr>		</tr>
	<tr>		<tr>
	<td>Exclusive</td>		<th>Exclusive</th>
	<td>Object is locked in exclusive mode.<br/>This level prohibits others from holding either an <var>Exclusive</var> lock or a <var>Share</var> lock. It is generally used for update. <var>Find And Reserve</var> statements acquire this type of record lock.</td>		<td>Object is locked in exclusive mode.<br/>This level prohibits others from holding either an <var>Exclusive</var> lock or a <var>Share</var> lock. It is generally used for update. <var>Find And Reserve</var> statements acquire this type of record lock.</td>
	</tr>		</tr>

Alex at 12:57, 30 August 2012

2012-08-30T12:57:47Z

← Older revision		Revision as of 12:57, 30 August 2012
Line 17:		Line 17:
	</tr>		</tr>
	</table>		</table>
			Typically, exclusive locks are used when there is an intent to update one or more of the records referenced by an object. A share lock is used to ensure a consistent view of records associated with an object, as such a lock prevents any other user from updating those records since an update requires an exclusive lock on a record. Unlocked (LockStrength None) records can be used where mechanisms other than locking are used to protect the integrity of field references, or in cases where an object is used to reference one or more records but the records are temporarily locked in share mode when they are actually referenced. The [[LoopLockStrength_(Record_property)\|Record]] and [[LoopLockStrength_(Recordset_property)\|Recordset]] class LoopLockStrength properties facilitate this kind of processing.

	'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|"Common enumeration methods"]].		'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|"Common enumeration methods"]].

Alex at 12:50, 30 August 2012

2012-08-30T12:50:02Z

← Older revision		Revision as of 12:50, 30 August 2012
Line 1:		Line 1:
	<!-- LockingStrength enumeration -->		<!-- LockingStrength enumeration -->
	This enumeration is used to indicate the strength of a lock, and is often used in controlling locking for [[Record_class\|Records]] and [[Recordset_class\|Recordsets]].		This enumeration is used to indicate the strength of a lock, and is often used in controlling locking for [[Record_class\|Records]] and [[Recordset_class\|Recordsets]]. When an object referencing one or more records is instantiated, the referenced records are locked with a particular lock strength, either implicitly as with the <var>Find All Records</var> and <var>Find And Reserve</var> statements or explicitly as with the [[New_(Record_constructor)\|Record]] and [[New_(Recordset_constructor)\|Recordset]] class constructors.

	These are the valid values of this [[Enumerations\|enumeration]], which correspond to standard <var class="product">Model 204</var> record-locking levels:		These are the valid values of this [[Enumerations\|enumeration]], which correspond to standard <var class="product">Model 204</var> record-locking levels:
	<table>		<table>

Alex at 12:06, 30 August 2012

2012-08-30T12:06:55Z

← Older revision		Revision as of 12:06, 30 August 2012
Line 1:		Line 1:
	~~#REDIRECT~~ [[~~New~~ (~~Recordset constructor~~)#~~LockStrength~~ enumeration]]		<!-- LockingStrength enumeration -->
			This enumeration is used to indicate the strength of a lock, and is often used in controlling locking for [[Record_class\|Records]] and [[Recordset_class\|Recordsets]].
			These are the valid values of this [[Enumerations\|enumeration]], which correspond to standard <var class="product">Model 204</var> record-locking levels:
			<table>
			<tr>
			<td>None</td>
			<td>Object is not locked.<br/>No locks are held on the object, so there can be no conflict with others holding <var>Share</var> or <var>Exclusive</var> locks (readers and updaters may proceed). <var>Find Without Locks</var> statements acquire this type of record lock for Recordsets.</td>
			</tr>
			<tr>
			<td>Share</td>
			<td>Object is locked in share mode.<br/>This level allows other users to hold a Share lock, but not an Exclusive lock (allows readers but not updaters to proceed). <var>Find All Records</var> statements acquire this type of record lock for Recordsets.</td>
			</tr>
			<tr>
			<td>Exclusive</td>
			<td>Object is locked in exclusive mode.<br/>This level prohibits others from holding either an <var>Exclusive</var> lock or a <var>Share</var> lock. It is generally used for update. <var>Find And Reserve</var> statements acquire this type of record lock.</td>
			</tr>
			</table>
			'''Note:''' As with all enumerations, the <var>ToString</var> method implicitly converts an enumeration value to a character string whose value is the name of the enumeration value. For more information about methods available to all enumerations, see [[Enumerations#Common enumeration methods\|"Common enumeration methods"]].

Dme: moved Lockstrength enumeration to LockStrength enumeration

2012-02-07T20:22:44Z

moved Lockstrength enumeration to LockStrength enumeration

← Older revision	Revision as of 20:22, 7 February 2012
(No difference)

JAL2: Redirected page to New (Recordset constructor)#LockStrength enumeration

2011-05-17T23:56:33Z

Redirected page to New (Recordset constructor)#LockStrength enumeration

New page

#REDIRECT [[New (Recordset constructor)#LockStrength enumeration]]