Miner.Responder.Shared Namespace : SubmitRuleException Class |
'Declaration
<System.SerializableAttribute()> Public Class SubmitRuleException Inherits Miner.Data.Access.RuleException
'Usage
Dim instance As SubmitRuleException
[System.Serializable()] public class SubmitRuleException : Miner.Data.Access.RuleException
public class SubmitRuleException = class(Miner.Data.Access.RuleException)
System.SerializableAttribute() public class SubmitRuleException extends Miner.Data.Access.RuleException
[System.Serializable()] public __gc class SubmitRuleException : public Miner.Data.Access.RuleException
[System.Serializable()] public ref class SubmitRuleException : public Miner.Data.Access.RuleException
Submit rule processing against a DataSet was originally setup so that any exception that was thrown would terminate the processing loop and return the error to the calling application. The problem with this approach is that it is too easy to write a rule with an insignificant bug (such as improper handling of deleted rows) that can leave the database in an incorrect state. This is particularly true since we do not currently support compensating transactions.
System.Object
System.Exception
Miner.Responder.Shared.SubmitRuleException
Miner.Responder.Shared.Exceptions.IncidentNotFound
Miner.Responder.Shared.Exceptions.OperationCanNotBeinthePast
Miner.Responder.Shared.Exceptions.OperationNotAllowedException
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2