All Versions
25
Latest Version
Avg Release Cycle
102 days
Latest Release
-

Changelog History
Page 2

  • v2.2.0.0 Changes

    December 03, 2015
    • ➕ Added support for RethinkDB 2.2
    • ➕ Added new commands serverInfo, uuid5 and value
  • v2.1.0.2 Changes

    August 26, 2015
    • 🔄 Change bounds on vector dependency
  • v2.1.0.1 Changes

    August 21, 2015
    • 🚀 Point release to fix synopsis on hackage.
  • v2.1.0.0 Changes

    • ➕ Added support for new RethinkDB 2.1 features (http://rethinkdb.com/blog/2.1-release/)
    • ➕ Added new ReQL terms floor, ceil, and round
    • 🔄 Changed UseOutdated optarg to ReadMode optarg
    • Enabled TCP Keepalive
  • v2.0.0.0 Changes

    • ➕ Added support for new RethinkDB 2.0 features (http://rethinkdb.com/blog/2.0-release/)
    • switch forEach args to match map
    • ➕ Added support for ghc 7.10
    • 👉 use Text instead of String for dbCreate and indexCreate for consistency
    • 👉 Make Line and Polygon new types
  • v1.16.0.0 Changes

  • v1.15.2.1 Changes

    • 🛠 Fix FromDatum Rational instance
    • Increase upper bound for network
    • 👍 Replace "mempty" with a better error message in FromDatum instances
    • ✂ Removed broken FromJSON and ToJSON instances for LonLat
    • 👌 Support Line and Polygon in FromDatum (Vector a)
    • ➕ Added FromDatum and ToDatum for LonLat
  • v1.15.2.0 Changes

    • group and mapReduce generate more efficient code
    • 🐎 Set NoDelay socket option, which significantly improves performance.
    • 🛠 Fix broken indexStatus and indexWait commands.
    • 🛠 Fix and improve benchmark script.
  • v1.15.1.0 Changes

    • 🛠 Fix compile error with GHC 7.8
    • Simplify Result instances
    • ➕ Add documentation to run
    • Replace the Result (Either a b) instance with something more useful
  • v1.15.0.0 Changes

    • 🚀 Redesigned and improved most of the API. This release is not backwards compatible.
    • ➕ Added all missing ReQL operations for RethinkDB 1.15 such as binary data, http, changes and geospatial operations
    • Switched to the JSON protocol