Chicken Scheme and CouchDB
I’ve recently been playing around with Chicken Scheme, leaving poor Clojure all high and dry (minus some visits to the newly started DFW-Clojure User Group). After building a service in C at work, I’ve caught the high-performance bug and Clojure hasn’t particularly been helpful in that regard. I’ve also found Chicken Scheme to be very simple with a more straightforward syntax than Clojure. I’ll still use Clojure, and am using it on a web-app side-project, but client side I’m really digging Chicken.
I’ve also been using MongoDB, but (OMG!) there’s no driver currently for MongoDB in Chicken Scheme. Until I have the chops to write my own version, I decided I might as well learn a similar DB: enter Couch. In my naive view, it’s very similar to Mongo - it’s a document-oriented database with JSON (or variation thereof) as its representative data structure. Even cooler, it’s already been ported to BlackBerry 10. This gives me some really good ideas for new projects.
I’m currently running Linux Mint, a “fork” of Ubuntu, so this setup guide follows what was necessary for me to get up and going with Chicken Scheme and CouchDB.
There are two options. The easy way:
This installs everything for you with no issue, however it’s an older version (as seems to be a common issue with the Ubuntu repositories). At the time of writing it’s at 4.7.0. You can also install Chicken by compiling from source. Download the tarball from call-cc.org, untar, and follow the INSTALL instructions. Easy!
Chicken Scheme has an extension system which packages and distributes “eggs.” An egg consists of Scheme sources plus some meta information such as build scripts and egg dependencies. You can install an egg using the chicken-install utility that comes with Chicken.
This will download the couchdb egg along with all eggs in the dependency tree. The utility then begins compiling and installing all eggs along the way. If you don’t do a lot of development, chances are likely that you will run into system dependencies that are unmet. Chicken Scheme compiles to C, and as such many eggs have dependencies on C libraries.
The one I hit with couchdb in particular was openssl. These system lib dependencies can be a little tricky to identify. Two tips:
- See which egg is failing, then find it in the egg index and look through it’s notes which /usually/ indicate dependencies
- Read the error message and decipher from there.
For example, my first attempt at installing the couchdb egg failed due to missing openssl header files. The install utility was attempting to compile the openssl egg, which was a dependency of the http-client egg, which is a dependency of the couchdb egg.
A few searches for openssl and I satisfied the dependency with the following command:
With that successfully in place, another call to install the couchdb egg succeeded.
I didn’t have time to compile and install a CouchDB server on my machine, so to the cloud I went. I signed up for an account at cloudant.com which provides a free-for-small-databases CouchDB compatible database. After signing up, I imported the example database aptly named “crud” and began toying around.
Booting up csi, the Chicken Scheme interpreter, I called
(use couchdb) and set out to play. The first hurdle: making a connection. The current documentation says to use something along the lines of
(define couch (make-connection “databasename” “http://localhost:123“)).
That failed miserably.
No matter what I tried, the command
(get-server-info couch) would fail with a connection refused.
(connection-uri couch) showed that the URI struct was still pointing at localhost. Luckily, the source for Chicken eggs are available, even for CouchDB. The make-connection function is created by the
(defstruct connection …) expression. I noticed that the server attribute of connection struct is a
uri-reference, not a string. Reading through the defstruct docs I figured out the following worked - woot.
This returns JSON data in Scheme structure:
Since I’m new to Scheme, getting the data out was a bit odd, and I’m sure completely inefficient.
That about sums it up. Hopefully I figure more stuff out and post some updates. Feel free to comment if I’m reading the JSON structure in a completely asinine way. The vector->list doesn’t seem right.
The couchdb egg documentation has been updated to cover most of this. I’ve also noticed a generally handy function that is exported by the couchdb module, json-ref, that makes it simple to grab top-level JSON items like “version” above.