Entities can be marked for deletion by using the Delete method, but will not be removed from the server until SaveChanges is called.
{CODE deleting_1@ClientApi\Session\DeletingEntities.cs /}
| Parameters | ||
|---|---|---|
| entity | T |
instance of the entity to delete |
| id | string |
ID of the entity to delete |
| expectedChangeVector | string |
a change vector to use for concurrency checks |
{CODE-TABS} {CODE-TAB:csharp:Sync deleting_2@ClientApi\Session\DeletingEntities.cs /} {CODE-TAB:csharp:Async deleting_2_async@ClientApi\Session\DeletingEntities.cs /} {CODE-TABS/}
{NOTE: Concurrency on Delete}
If UseOptimisticConcurrency is set to 'true' (default 'false'), the Delete() method will use loaded 'employees/1' change vector for concurrency check and might throw ConcurrencyException.
{NOTE/}
{CODE-TABS} {CODE-TAB:csharp:Sync deleting_3@ClientApi\Session\DeletingEntities.cs /} {CODE-TAB:csharp:Async deleting_3_async@ClientApi\Session\DeletingEntities.cs /} {CODE-TABS/}
{NOTE: Concurrency on Delete}
In this overload, the Delete() method will not do any change vector based concurrency checks because the change vector for 'employees/1' is unknown.
{NOTE/}
{INFO:Information}
If entity is not tracked by session, then executing:
{CODE deleting_4@ClientApi\Session\DeletingEntities.cs /}
is equal to doing:
{CODE deleting_5@ClientApi\Session\DeletingEntities.cs /}
{NOTE: Change Vector in DeleteCommandData}
In this sample the change vector is null - this means that there will be no concurrency checks. A non-null and valid change vector value will trigger a concurrency check.
{NOTE/}
You can read more about defer operations here.
{INFO/}