> I'm wondering: how would you compare the use of ClojureQL and clj- > record(which sadly doesn't show much activity currently)? Isn't CQL > going back to the SQL level or database queries, whereas clj-record is > at a higher level? Would it be easy to code this higher level layer on > top of cql? Or is that less important in Clojure than it is in OO > languages?
I'm not familiar with the Ruby version, so going from the description on the wiki its a persistence library which only does some SQL interaction if you write conversion fn yourself. Emphasis is on the persistence bit. On the other hand ClojureQL is strictly an SQL-Statement-Compiler, which comes with its own SQL syntax, ie (query table1 [row1 row2] (> row1 row2)) for instance. Once you've learned this syntax, which should come naturally for Clojurians, ClojureQL will make sure that it translates into sane SQL statements for a multitude of backends, meaning you don't ever have to worry about SQL again. I think your explanation of high-/low-level is correct and I think it would be easy(er) to built something like that on top of ClojureQL, but I haven't looked into it. > And a suggestion: having migrations in CQL would be great! Could you elaborate a little? /Lau -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
