 | UpstreamDiagnosticRepositoryDelete Method |
Delete the specified identified data
Namespace: SanteDB.Client.Upstream.ManagementAssembly: SanteDB.Client (in SanteDB.Client.dll) Version: 3.0.2081-alpha+027e4605b77f83de5445cbcd55717223932d2452
Syntaxpublic DiagnosticReport Delete(
Guid key,
TransactionMode transactionMode,
IPrincipal principal
)
Public Function Delete (
key As Guid,
transactionMode As TransactionMode,
principal As IPrincipal
) As DiagnosticReport
public:
virtual DiagnosticReport^ Delete(
Guid key,
TransactionMode transactionMode,
IPrincipal^ principal
) sealed
abstract Delete :
key : Guid *
transactionMode : TransactionMode *
principal : IPrincipal -> DiagnosticReport
override Delete :
key : Guid *
transactionMode : TransactionMode *
principal : IPrincipal -> DiagnosticReport Parameters
- key Guid
- The identifier/key of the data to be deleted
- transactionMode TransactionMode
- The transaction mode
- principal IPrincipal
- The principal which is deleting the data
Return Value
DiagnosticReport[Missing <returns> documentation for "M:SanteDB.Client.Upstream.Management.UpstreamDiagnosticRepository.Delete(System.Guid,SanteDB.Core.Services.TransactionMode,System.Security.Principal.IPrincipal)"]
Implements
IDataPersistenceServiceTDataDelete(Guid, TransactionMode, IPrincipal)
Remarks
This method will attempt to delete data according to the currently scoped DataPersistenceControlContext.
| LogicalDelete | The persistence layer should attempt to logically delete the record. This means that the record should not appear in queries, nor direct retrieves |
| PermanentDelete | The persistence layer should purge the data from the database |
The DeleteMode is a suggestion to the persistence layer, generally the closest, most appropriate value
is chosen based on:
- Whether the TData class can be logically deleted (i.e. does it carry the necessary fields to support deletion)
- Whether there are other references to the object
- Whether the configuration for the persistence layer permits logical deletion
See Also