You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Docs/reference/content/what_is_new.md
+8-7Lines changed: 8 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,8 @@ title = "What's New"
12
12
13
13
Some of the changes in 2.10.0 include:
14
14
15
-
*[Client-side field level encryption support]({{< relref "reference\driver\crud\client_side_encryption.md" >}}) for Windows
15
+
*[Client-side field level encryption support]({{< relref "reference\driver\crud\client_side_encryption.md" >}}) for Windows
16
+
* Added new ReplaceOptions parameter for the ReplaceOne CRUD methods
16
17
17
18
## What's New in 2.9.0
18
19
@@ -111,7 +112,7 @@ ReadPreference has a new MaxStaleness property that can be used when reading fro
111
112
112
113
### New Linearizable ReadConcernLevel
113
114
114
-
There is a new ReadConcernLevel called Linearizable in addition to the existing Local and Majority levels. You specify the read concern level by assigning a value to
115
+
There is a new ReadConcernLevel called Linearizable in addition to the existing Local and Majority levels. You specify the read concern level by assigning a value to
115
116
the ReadConcernLevel property of a ReadConcern value.
116
117
117
118
### Support for collations
@@ -179,7 +180,7 @@ In earlier versions of the driver the aggregate fluent API had methods supportin
179
180
executed when the aggregate fluent object was executed, but there was no way to build a standalone pipeline value.
180
181
181
182
With the introduction of the CreateView method and Facet pipeline operators there is now a need to create
182
-
pipelines separately from the aggregate fluent API.
183
+
pipelines separately from the aggregate fluent API.
183
184
184
185
The new PipelineDefinitionBuilder class can be used to create pipelines.
185
186
@@ -209,7 +210,7 @@ The 2.3.0 driver is a minor release with few new features. The most notable is d
209
210
210
211
You can now use the .NET driver with .NET Core.
211
212
212
-
The Nuget packages target two versions of the .NET frameworks: net45 and netstandard1.5. The net45 target allows the driver to be used with the full .NET Framework
213
+
The Nuget packages target two versions of the .NET frameworks: net45 and netstandard1.5. The net45 target allows the driver to be used with the full .NET Framework
213
214
version 4.5 and later, and the netstandard1.5 target allows the driver to be used with any framework that supports netstandard1.5, which includes .NET Core 1.0.
214
215
215
216
## What's New in 2.2.0
@@ -249,7 +250,7 @@ The 2.0.0 driver ships with a host of new features. The most notable are discuss
249
250
### Async
250
251
251
252
As has been requested for a while now, the driver now offers a full async stack. Since it uses Tasks, it is fully usable
252
-
with async and await.
253
+
with async and await.
253
254
254
255
While we offer a mostly backwards-compatible sync API, it is calling into the async stack underneath. Until you are ready
255
256
to move to async, you should measure against the 1.x versions to ensure performance regressions don't enter your codebase.
@@ -258,7 +259,7 @@ All new applications should utilize the New API.
258
259
259
260
### New API
260
261
261
-
Because of our async nature, we have rebuilt our entire API. The new API is accessible via MongoClient.GetDatabase.
262
+
Because of our async nature, we have rebuilt our entire API. The new API is accessible via MongoClient.GetDatabase.
262
263
263
264
- Interfaces are used ([`IMongoClient`]({{< apiref "T_MongoDB_Driver_IMongoClient" >}}), [`IMongoDatabase`]({{< apiref "T_MongoDB_Driver_IMongoDatabase" >}}), [`IMongoCollection<TDocument>`]({{< apiref "T_MongoDB_Driver_IMongoCollection_1" >}})) to support easier testing.
264
265
- A fluent Find API is available with full support for expression trees including projections.
@@ -298,7 +299,7 @@ We've also include some experimental features which are subject to change. These
298
299
#### Logging
299
300
300
301
It is possible to see what is going on deep down in the driver by listening to core events. We've included a simple text logger as an example:
0 commit comments