v0.10.0.0

Features

• Added support for RethinkDB changefeeds via table.Changes(). This allows a client application to monitor and receive changes to a RethinkDB table as they happen. Issue #180
• Added a "queryTimeout" option to the connectionPool configuration element, which is the time in seconds that each query is allowed to execute before it is timed out from the client. Thanks to Lucas Jans for the contribution. PR #188
• Add support for Enumerable.Any() and Enumerable.Contains() methods to be mapped into a RethinkDB "contains" query term. Issue #196
• Add a new "StreamChanges" and "StreamChangesAsync" extension methods to IConnection, which do not use the connection's query timeout when executing server-side commands. Issue #193
• Allow the Changes query command to be run against any query that returns a sequence of objects, rather than just a table. This is supported as-of RethinkDB 1.16. Issue #190
• Compatibility with RethinkDB 1.16. PR #200
• Compatibility with RethinkDB 2.0. PR #207

Breaking Changes

• RethinkDB 1.16 changed the DML response to use the fields "dbs_created", "dbs_dropped", "tables_created", and "tables_dropped" in preference over the "created" and "dropped" fields. To support this, RethinkDb.DmlREsponse now has four additional fields that map to these values. The old fields, Created and Dropped, are still used to report on index operations. PR #200
• Fields in DmlResponse class have been changed from type double to type uint where they represent the count of things. PR #205

Bugfixes

• Fix errors that occur when writing obvious filters like ... == null and field.HasValue. Issue #203 & PR #204