Support passing binary objects directly to queries

Author: norpan

lib/rethinkdb/prepare.ex

@@ -39,6 +39,10 @@ defmodule RethinkDB.Prepare do
     {[k,v], state}
   end
   defp prepare(el, state) do
-    {el, state}
+    if is_binary(el) and not String.valid?(el) do
+      {RethinkDB.Query.binary(el), state}
+    else
+      {el, state}
+    end
   end
 end

lib/rethinkdb/query.ex

@@ -189,10 +189,11 @@ defmodule RethinkDB.Query do
   Encapsulate binary data within a query.
 
   The type of data binary accepts depends on the client language. In
-  Elixir, it expects a Binary. Using a Buffer object within a query implies the use of binary and the ReQL driver will automatically perform the coercion.
+  Elixir, it expects a Binary. Using a Binary object within a query implies
+  the use of binary and the ReQL driver will automatically perform the coercion.
 
-  Binary objects returned to the client in JavaScript will also be Node.js
-  Buffer objects. This can be changed with the binaryFormat option provided
+  Binary objects returned to the client in Elixir will also be
+  Binary objects. This can be changed with the binary_format option :raw
   to run to return “raw” objects.
 
   Only a limited subset of ReQL commands may be chained after binary:

test/query/control_structures_test.exs

@@ -37,6 +37,16 @@ defmodule ControlStructuresTest do
     assert data == result
   end
 
+  test "binary native no wrapper" do
+    d = << 220, 2, 3, 4, 5, 192 >>
+    q = d
+    {:ok, %Record{data: data}} = run q
+    assert data == d
+    q = data
+    {:ok, %Record{data: result}} = run q, [binary_format: :native]
+    assert data == result
+  end
+
   test "do_r" do
     q = do_r fn -> 5 end
     {:ok, %Record{data: data}} = run q