👁 Image
RethinkDb.Driver 2.3.150

• .NETFramework 4.5

  • Common.Logging (>= 3.3.0)
  • Newtonsoft.Json (>= 10.0.3)

• .NETStandard 2.0

  • Microsoft.Extensions.Logging.Abstractions (>= 2.0.0)
  • Newtonsoft.Json (>= 10.0.3)

## v2.3.150
* Issue #146 - Better support for `CancellationToken`. Clean up of token registrations that may produce exceptions when `CancellationTokenSource.Cancel()` is called.

## v2.3.101
* Issue #143 - `ConnectionPool.Builder.ConnectAsync()` now respects `.InitialTimeout()` parameter. `CancellationToken` also supported.

## v2.3.100
* First batch of expired commercial licenses have been banned for use.
* Issue #139 - New `.RunUnsafeAsync` run helper that runs a query on the server and returns the raw `Response` object in an unsafe way with minimal client-side processing. The unbridled use of this method can lead to memory leaks on both the client and server. Use with extreme caution. This method should only be used in well-understood and advanced scenarios.
* **POSSIBLE BREAKING CHANGE:** `.RunResult` for `Result` (DML) type responses that correspond to inserts, deletes, updates has been renamed to `.RunWrite`. Please use the new method name instead. **Note:** The `.RunResult<T>` for `T` type responses will not be obsoleted. The reason for the former `.RunResult` method rename is to avoid confusion between `.RunResult` and `.RunResult<T>`. The obsoleted methods produce compiler warnings in this version. If no compiler warnings are produced, no changes are necessary. The obsolete methods will be removed in the next major RethinkDB driver release (2.4).

## v2.3.24
* Issue #138 - Better error handling in cursors.
* **POSSIBLE BREAKING CHANGE:** Previously, when an error response was received during cursor enumeration a `NotSupportedException` was thrown. Issue #138 changes this behavior by throwing more detailed (and more specific) exception based on the response from the server. For example, the driver will throw a `ReqlOpFailedError` exception if a cursor change feed is interrupted behind a RethinkDB proxy instead of throwing a generic `NotSupportedException`.

## v2.3.23
* Issue #128 - NullReferenceException when executing query after failed reconnect.
* Renamed `val` parameters on `Connection.Builder` for better readability and IntelliSense.


Full History Here: https://github.com/bchavez/RethinkDb.Driver/blob/master/HISTORY.md