The library formerly known as clojure.contrib.sql has had its first non-snapshot release. Features added (above and beyond clojure.contrib.sql): returns generated keys for single record inserts supports naming strategies to allow you to override the conversion of keywords to/from SQL entity names exposes resultset-seq that respects naming strategies exposes print-* functions to print SQL exceptions (and no longer prints to *err* on an exception) You can read more about naming strategies in the clojure.ja[...]

As folks have no doubt realized, I'm using Clojure more and more these days and just embarked on a project at work to replace the CFML-based ORM "Reactor" in our codebase with a much more lightweight ORM written in Clojure (enclosed in a lightweight CFML wrapper). While I've been sketching out the code for that, I've been using the clojure.contrib.sql library, one of a fairly large selection of somewhat ad hoc utilities contributed over the last several years by various Clojure community members. As part o[...]

A discussion that crops up from time to time is whether primary keys should be UUIDs or simple auto-incrementing integers. There are pros and cons on both sides. UUIDs provide universal uniqueness which allows data to be stored across multiple databases, merged and so on. Auto-increment primary keys are easy to work with and efficient for indexing - but cause problems when you need to deal with data created across multiple databases, such as data migration and merging. UUIDs, as 36 character strings, take [...]