Abstracting Data Query in Ruby with Ambition Ambition
Chris Wanstrath brings his own solution: Ambition. Ambition takes advantage of ParseTree to walk the parse tree and translate plain Ruby queries into SQL (when the target is a Relational Database), so at the end you'll be able to write your queries the Ruby way:
User.first
# which will translate into "SELECT * FROM users LIMIT 1"
User.select { |u| u.karma > 20 }.sort_by(&:karma).first(5)
# which will translate into "SELECT * FROM users WHERE (users.`karma` > 20)
# ORDER BY users.karma LIMIT 5" While originally Chris was gunning for Rack, he changed his target since he discovered LINQ.
We’ve moved our sights from Rack to LINQ. That is, we don’t want to only support other ORMs—we want Ambition to be a query language for SQL, LDAP, XPath, the works. The 1.0 release will be backend-agnostic. Maybe then we’ll change the name to Hubris? Time will tell.You can find latest sources at
git://errtheblog.com/git/ambition
Another Groovy plug :)
by
Thom Nichols
At some point GORM will support JPA, which (if I understand correctly) means it should be able to query XML and such as well.
Re: Another Groovy plug :)
by
Werner Schuster
However, Ambition works by actually looking at the AST of the queries, and as such is similar to Macros in languages like LISP or Scheme. The link to LINQ (pun intended) is that LINQ uses the same approach.
Of course, the results of the various solutions are the same, but the approaches are different. Question is how well Ruby syntax lends itself to Macros: the Ambition queries still need to be legal Ruby code, otherwise it couldn't be parsed. This is different in LISP, since there isn't much syntax to speak of in the first place. Of course, taking a peek at LINQ can help here.
Educational Content
Writing Usable APIs in Practice
Giovanni Asproni May 19, 2013
Concurrency in Clojure
Stuart Halloway May 17, 2013




Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think