Specifying the sql is a bit clumsy (IMHO), but it works, and ...

Specifying the sql is a bit clumsy (IMHO), but it works, and it's NOT bad, at all. I think the utility would be improved by finding a better (less cryptic) way of specifying the sql (e.g. the find_all() function) for a query. Though this is a problem ultimately in designing any dB class (which I've done often enough to not want to bother any more :) ). Just a suggestion: break the parts of the query up into sub-objects in their own right. FROM tables, JOIN, INNER-JOIN, OUTER-JOIN, FILTER (just the actual filter, not the relationship specs between tables involved in the query), and so. This improves over all utility, in my experience with query objects. Also allows for vastly more complex queries, involving multiple tables or dB objects (views, etc).

Anyway... nice job!

Thanks.
Yah, I wanted to do something like that (like the Kohana frameworks DB class), but I decided to just make it way simpler.