Awesome

cl-rethinkdb - RethinkDB driver for Common Lisp

This is an async RethinkDB driver for everyone's favorite programming language. It does its best to follow the query language specification. If it's missing any functions or has implemented any of them incorrectly, please open an issue.

This driver is up to date with RethinkDB's v2.0.x protocol.

As with most of my drivers, cl-rethinkdb requires cl-async, and makes heavy use of cl-async's promises.

This driver is built so that later on, more than one TCP backend can be used. Right now, the only one implemented is cl-async, but usocket/IOLib could just as easily be used if someone puts in the time.

Documentation

The driver makes extensive use of promises, as mentioned, so be sure to know your way around the promise syntax macros when using it.

Everything needed to use the driver is exported out of the cl-rethinkdb package, which has the nickname r.

DSL

cl-rethinkdb makes use of a query DSL that maps keyword function calls to normal function calls. It does this so that predefined common lisp functions can be used instead of giving them rediculous names to avoid naming clashes.

The DSL is activated by using either the r macro (used to build query forms) or the fn macro (used to build anonymous functions).

Note that this section only covers the DSL itself. Check out the full list of commands to start building the query of your dreams.

r (macro)

This macro translates keyword functions into ReQL function calls:

;; grab first 10 records from the `users` table
(r (:limit (:table "users") 10))

This translates to

(cl-rethinkdb-reql::limit (cl-rethinkdb-reql::table "users") 10)

fn (macro)

This macro creates an anonymous function for use in a RethinkDB query.

It works very much like the r macro, and in fact wraps its inner forms in r so that you can use the query DSL from within a function.

;; return an anonymous function that adds `3` to the given argument
(fn (x) (:+ x 3))

Functions can be mixed in with r queries:

;; find all users older than 24
(r (:filter (:table "users")
            (fn (user)
              (:< 24 (:attr user "age")))))

Note how inside the fn body, we're still using functions prefixed with :.

Sending queries and getting results

Once you've constructed a query via r, you need to send it to the server. When the server responds successfully, you will get either an atom (a single value: integer, boolean, hash, array, etc). or a cursor which provides an interface to iterate over a set of atoms.

connect (function)

(defun connect (host port &key db use-outdated noreply profile read-timeout auth))
  => promise (tcp-socket)

Connects a socket to the given host/port and returns a promise that's finished with the socket.

Usage:

(alet ((sock (connect "127.0.0.1" 28015 :db "test")))
  ;; ... do stuff ...
  (disconnect sock))

run (function)

(defun run (sock query-form))
  => promise (atom/cursor profile-data)

Run a query against the given socket (connected using connect). Returns a promise finished with either the atom the query returns or a cursor to the query results.

If profile is t when calling connect, the second promise value will be the profile data returned with the query.

run can signal the following errors on the promise it returns:

• query-client-error
• query-compile-error
• query-runtime-error

Example

(alet* ((sock (connect "127.0.0.1" 28015))
        (query (r (:get (:table "users") 12)))  ; get user id 12
        (value (run sock query)))
  (format t "My user is: ~s~%" value)
  (disconnect sock))

wait-complete (function)

(defun wait-complete (sock))
  => promise (t)

Waits for all queries sent on this socket with noreply => t to finish. This lets you queue up a number of write operations on a socket. You can then call wait-complete on the socket and it will return the response when all the queued operations finish.

cursor (class)

The cursor class keeps track of queries where a sequence of results is returned (as opposed to an atom). It is generally opaque, having no public accessors.

Cursor functions/methods:

• cursorp
• next
• has-next
• to-sequence
• to-array
• each
• stop
• stop/disconnect

cursorp (function)

(defun cursorp (cursor))
  => t/nil

Convenience function to tell if the given object is a cursor.

next (function)

(defun next (sock cursor))
  => promise (atom)

Gets the next result from a cursor. Returns a promise that's finished with the next result. The result could be stored locally already, but it also may need to be retrieved from the server.

next can signal two errors on the promise it returns:

• cursor-overshot
• cursor-no-more-results

(alet* ((sock (connect "127.0.0.1" 28015))
        (query (r (:table "users")))  ; get all users
        (cursor (run sock query)))
  ;; grab the first result from the cursor.
  (alet ((user (next sock cursor)))
    (format t "first user is: ~s~%" user)
    ;; let's grab another user
    (alet ((user (next sock cursor)))
      (format t "second user is: ~s~%" user)
      ;; let the server/driver know we're done with this result set
      (stop/disconnect sock cursor))))

has-next (function)

(defun has-next (cursor))
  => t/nil

Determines if a cursor has more results available.

to-sequence (function)

(defun to-sequence (sock cursor))
  => promise (sequence)

Given a socket and a cursor, to-sequence grabs ALL the results from the cursor, going out to the server to get more if it has to, and returns them as a sequence through the returned promise. The sequence type (vector/list) depends on the value of *sequence-type*.

to-array (function)

(defun to-array (sock cursor))
  => promise (vector)

Given a socket and a cursor, to-array grabs ALL the results from the cursor, going out to the server to get more if it has to, and returns them as an array through the returned promise.

(alet* ((sock (connect "127.0.0.1" 28015))
        (query (r (:table "users")))  ; get all users
        (cursor (run sock query))
        (all-records (to-array sock cursor)))
  (format t "All users: ~s~%" all-records)
  ;; cleanup
  (stop/disconnect sock cursor))

Don't call to-array on a cursor returned from a changefeed. It will just sit there endlessly saving results to a list it will never return.

each (function)

(defun each (sock cursor function))
  => promise 

Call the given function on each of the results of a cursor. The returned promise is finished when all results have been iterated over.

(alet* ((sock (connect "127.0.0.1" 28015))
        (cursor (run sock (r (:table "users")))))
  ;; print each user
  (wait (each sock cursor
          (lambda (x) (format t "user: ~s~%" x)))
    ;; cleanup
    (wait (stop sock cursor)
      (disconnect sock))))

each is the function you want to use for listening to changes on a cursor that is returned from a changefeed.

stop (function)

(defun stop (sock cursor))
  => promise

Stops a currently open query/cursor. This cleans up the cursor locally, and also lets RethinkDB know that the results for this cursor are no longer needed. Returns a promise that is finished with no values when the operation is complete.

stop/disconnect (function)

(defun stop/disconnect (sock cursor))
  => nil

Calls stop on a cursor, and after the stop operation is done closes the passed socket. Useful as a final termination to an operation that uses a cursor.

Note that this function checks if the object passed is indeed a cursor, and if not, just disconnects the socket without throwing any errors.

disconnect (function)

(defun disconnect (sock))
  => nil

Disconnect a connection to a RethinkDB server.

Binary data

Binary data is now part of the driver. Using it is simple...you pass in an unsigned byte array (ie (simple-erray (unsigned-byte 8) (*))) and the driver will handle encoding of the binary data for you. Binary data passed in must be of the unsigned-byte type, or your data will just be encoded as an array (or whatever type it actually is).

When an object is returned that has binary data, the driver converts it back to an unsigned byte array.

You can also force usage of the binary type by using the (:binary ...) type in the DSL. It takes 1 argument: a base64 string of your data. Note, however, that if you do use (:binary "ZG93biB3aXRoIHRoZSBvcHByZXNzaXZlIGNhcGl0YWxpc3QgcmVnaW1l"), when you pull that document out, the data will be encoded as a raw unsigned-byte array (not a base64 string).

Config

These mainly have to do with how you want data returned.

*sequence-type*

When a sequence is returned from RethinkDB, it can be either returned as a list (if *sequence-type* is :list or as a vector (if *sequence-type* is :array). It's really a matter of preference on how you're going to access the data. (But you may also want to read on-sequence-type for a warning about round tripping rethinkdb documents while using :list).

Default: :list

*object-type*

If an object (as in, key/value object) is returned from RethinkDB, it can be encoded as a hash table (if *object-type* is :hash) or as an association list (if *object-type* is :alist). Hash tables are almost always more performant, but alists can be easier to debug. Your choice.

Default: :hash

Thread safety

cl-rethinkdb stores all its global state in one variable: *state*, which is exported in the cl-rethinkdb package. The *state* variable is an instance of the cl-rethinkdb:state CLOS class. This lets you declare a thread-local variable when starting a thread so there are no collisions when accessing the library from multiple threads:

(let ((cl-rethinkdb:*state* (make-instance 'cl-rethinkdb:state)))
  (as:with-event-loop ()
    ;; run queries in this context
    ))

Using let in the above context declares *state* as a thread local variable, as opposed to using setf, which will just modify the global, shared context. Be sure that the let form happens at the start of the thread and encompasses the event loop form.

Commands

All of the following are accessible via the r DSL macro by prefixing the name with a :. So (table "users") becomes (:table "users").

These are almost 100% compatible with the ReQL specification, so if you familiarize yourself with the query language, you will automatically get a good handle on the following.

For a better understanding of the return types of the following commands, see the REQL type hierarchy in the protobuf specification.

• db (db-name) => database
• db-drop (db-name) => object
• db-list () => object
• table-create (db table-name &key datacenter primary-key durability) => object
• table-drop (db table-name) => object
• table-list (db) => object
• sync (table) => object
• index-create (table name &key function multi) => object
• index-drop (table name) => object
• index-list (table) => array
• index-status (table &rest names) => array
• index-wait (table &rest names) => array
• changes (select &key squash include-states) => cursor
• args (arg-list) => special
• binary (base64-string) => binary
• insert (table sequence/object &key conflict durability return-changes) => object
• update (select object/function &key non-atomic durability return-changes) => object
• replace (select object/function &key non-atomic durability return-changes) => object
• delete (select &key durability return-changes) => object
• db (db-name) => db
• table (db table-name &key read-mode identifier-format) => sequence
• get (table item-id) => object
• get-all (table key/keys &key index) => array
  (key/keys can be either a string type or a list of string types)
• between (sequence left right &key index) => sequence
• minval () => constant
• maxval () => constant
• filter (sequence object/function &key default) => sequence
• inner-join (sequence1 sequence2 function) => sequence
• outer-join (sequence1 sequence2 function) => sequence
• eq-join (sequence1 field sequence2 &key index) => sequence
• zip (sequence) => sequence
• map (sequence function) => sequence
• with-fields (sequence &rest strings) => sequence
• concat-map (sequence function) => sequence
• order-by (sequence field &rest fields) => sequence
• asc (field) => field
• desc (field) => field
• skip (sequence number) => sequence
• limit (sequence number) => sequence
• slice (sequence start end) => sequence
• nth (sequence number) => object
• offsets-of (sequence object/reql-function) => sequence
• is-empty (sequence) => boolean
• union (sequence &rest sequences) => sequence
• sample (sequence count) => sequence
• random (lower &optional upper &key float) => number
• group (sequence fields-or-functions &key index) => grouped_sequence
• ungroup (grouped-sequence) => sequence
• reduce (sequence function) => object
• count (sequence &optional object/reql-function) => number
• sum (sequence &optional field-or-function) => number
• avg (sequence &optional field-or-function) => number
• min (sequence &optional field-or-function) => type-of-object-in-sequence
• max (sequence &optional field-or-function) => type-of-object-in-sequence
• distinct (sequence) => sequence
• contains (sequence object) => boolean
• count-reduce () => function
• sum-reduce (field) => function
• avg-reduce (field) => function
• attr (object field) => object
• row (&optional field) => object
• pluck (sequence/object field &rest fields) => sequence/object
• without (sequence/object field &rest fields) => sequence/object
• merge (object &rest objects) => object
• append (array object) => array
• prepend (array object) => array
• difference (array1 array2) => array
• set-insert (array object) => array
• set-intersection (array1 array2) => array
• set-union (array1 array2) => array
• set-difference (array1 array2) => array
• has-fields (object string &rest strings) => bool
• insert-at (array index object) => array
• splice-at (array1 index array2) => array
• delete-at (array index) => array
• change-at (array index object) => array
• keys (object) => array
• object (key val &rest) => object
• \+ (number/string &rest numbers/strings) => number/string
• \- (number &rest numbers) => number
• \* (number &rest numbers) => number
• / (number &rest numbers) => number
• % (number mod) => number
• && (boolean &rest booleans) => boolean
• || (boolean &rest booleans) => boolean
• == (object &rest objects) => boolean
• != (object &rest objects) => boolean
• < (object &rest objects) => boolean
• <= (object &rest objects) => boolean
• > (object &rest objects) => boolean
• >= (object &rest objects) => boolean
• ~ (boolean) => boolean
• match (string string-regex) => object
• split (string &optional separator max-splits) => array
• upcase (string) => string
• downcase (string) => string
• now () => time
• time (timezone year month day &optional hour minute second) => time
• epoch-time (timestamp) => time
• iso8601 (date &key timezone) => time
• in-timezone (time timezone) => time
• timezone (time) => string
• during (time start end) => boolean
• date (time) => time
• time-of-day (time) => number
• year (time) => number
• month (time) => number
• day (time) => number
• day-of-week (time) => number
• day-of-year (time) => number
• hours (time) => number
• minutes (time) => number
• seconds (time) => number
• to-iso8601 (time) => string
• to-epoch-time (time) => number
• monday () => time
• tuesday () => time
• wednesday () => time
• thursday () => time
• friday () => time
• saturday () => time
• sunday () => time
• january () => time
• february () => time
• march () => time
• april () => time
• may () => time
• june () => time
• july () => time
• august () => time
• september () => time
• october () => time
• november () => time
• december () => time
• do (function &rest args) => object
• branch (boolean true-expr false-expr) => object
• for-each (sequence function) => object
• error (message) => error
• default (top1 top2) => top
• expr (lisp-object) => RethinkDB object
• js (javascript-str) => object/function
• coerce-to (object type) => object
• typeof (object) => type-string
• info (object) => object
• json (string) => object
• to-json-string (object) => string
• literal (&optional object) => object
• geojson (object)) => geometry
• to-geojson (geo)) => object
• point (lat long)) => geometry
• line (&rest array/geo)) => geometry
• polygon (&rest array/geo)) => geometry
• distance (geo-from geo-to &key geo-system unit)) => number
• intersects (geo1 geo2)) => bool
• includes (geo1 geo2)) => bool
• circle (geo radius &key num-vertices geo-system unit fill)) => geometry
• get-intersecting (table geo &key index)) => stream
• fill (geo)) => geometry
• get-nearest (table geo &key index max-results max-dist geo-system unit)) => array
• polygon-sub (geo1 geo2)) => geometry

Errors

These are the errors you may encounter while using this driver. Most (if not all) errors will be signalled on a promise instead of thrown directly. Errors on a promise can be caught via catcher.

query-error

A general query error.

query-client-error

extends query-error

Thrown when the driver sucks. If you get this, open an issue.

query-compile-error

extends query-error

Thrown when a query cannot compile. If you get this, take a close look at your query forms.

query-runtime-error

extends query-error

Thrown when the database has a runtime error.

cursor-error

A general error with a cursor.

cursor-overshot

extends cursor-error

Thrown when next is called on a cursor, but the cursor is currently grabbing more results.

cursor-no-more-results

extends cursor-error

Thrown when next is called on a cursor that has no more results. You can test this by using has-next.

reql-error

A REQL error. This is thrown when there's an error in the returned REQL data from the database. For instance, if a time value comes back without a timestamp or binary data type comes back without the payload. Generally, if the database itself is functioning correctly, you won't see this error.

License

MIT. Enjoy.