Pending session operations e.g. Store, Delete and many others will not be send to server till SaveChanges is called.
##Syntax
{CODE-TABS} {CODE-TAB:csharp:Sync saving_changes_1@ClientApi\Session\SavingChanges.cs /} {CODE-TAB:csharp:Async saving_changes_1_async@ClientApi\Session\SavingChanges.cs /} {CODE-TABS/}
###Example
{CODE-TABS} {CODE-TAB:csharp:Sync saving_changes_2@ClientApi\Session\SavingChanges.cs /} {CODE-TAB:csharp:Async saving_changes_2_async@ClientApi\Session\SavingChanges.cs /} {CODE-TABS/}
{PANEL:Waiting for Indexes}
You can ask the server to wait until the indexes are caught up with changes made within the current session before the SaveChanges returns.
- You can set a timeout (default: 15 seconds).
- You can specify whether you want to throw on timeout (default:
false). - You can specify indexes that you want to wait for. If you don't specify anything here, RavenDB will automatically select just the indexes that are impacted by this write.
{CODE-TABS} {CODE-TAB:csharp:Sync saving_changes_3@ClientApi\Session\SavingChanges.cs /} {CODE-TAB:csharp:Async saving_changes_3_async@ClientApi\Session\SavingChanges.cs /} {CODE-TABS/}
{PANEL/}
{PANEL:Waiting for Replication - Write Assurance}
Sometimes you might need to ensure that changes made in the session will be replicated to more than one node of the cluster before the SaveChanges returns.
It can be useful if you have some writes that are really important so you want to be sure the stored values will reside on multiple machines. Also it might be necessary to use
when you customize the read balance behavior and need to ensure the next request from the user
will be able to read what he or she just wrote (the next open session might access a different node).
You can ask the server to wait until the replication is caught up with those particular changes.
- You can set a timeout (default: 15 seconds).
- You can specify whether you want to throw on timeout, which may happen in case of network issues (default:
true). - You can specify to how many replicas (nodes) the currently saved write must be replicated, before the
SaveChangesreturns (default: 1). - You can specify whether the
SaveChangeswill return only when the current write was replicated to majority of the nodes (default:false).
{CODE-TABS} {CODE-TAB:csharp:Sync saving_changes_4@ClientApi\Session\SavingChanges.cs /} {CODE-TAB:csharp:Async saving_changes_4_async@ClientApi\Session\SavingChanges.cs /} {CODE-TABS/}
{WARNING:Important}
The WaitForReplicationAfterSaveChanges waits only for replicas which are part of the cluster. It means that external replication destinations are not counted towards the number specified in replicas parameter, since they are not part of the cluster.
{WARNING/}
{WARNING:Important}
Even if RavenDB was not able to write your changes to the number of replicas you specified, the data has been already written to some nodes. You will get an error but data is already there.
This is a powerful feature, but you need to be aware of the possible pitfalls of using it.
{WARNING/}
{PANEL/}
{PANEL:Transaction Mode - Cluster Wide}
Setting TransactionMode to TransactionMode.ClusterWide will enable the Cluster Transactions feature.
With this feature enabled the Session will support the following write commands:
Store/StoreAsyncDeleteCreateCompareExchangeValueUpdateCompareExchangeValueDeleteCompareExchangeValue
Here is an example of creating a unique user with cluster wide.
{CODE-TABS} {CODE-TAB:csharp:Sync cluster_store_with_compare_exchange@ClientApi\Session\SavingChanges.cs /} {CODE-TAB:csharp:Async cluster_store_with_compare_exchange_async@ClientApi\Session\SavingChanges.cs /} {CODE-TABS/}
{PANEL/}