It's funny, I actually didn't know about honeysql until today. When I found
out that it existed, I got a little excited that someone else also came to
the same conclusion independently. I think it says something good about
this approach.
As far as design decisions, I think OJ has a more minimalistic approach and
a stronger specification than honeysql. Also, OJ has support for nested
joins -
{:table :users, :join {:items {:user_id :id}}}
=> ({:username "blah" :items ({:id 1 :name "Thing"})} ...
On Tuesday, November 4, 2014 9:54:04 AM UTC-6, Niels van Klaveren wrote:
>
> Looks cool, any design decisions that made you create this instead of
> using honeysql <https://github.com/jkk/honeysql> ?
>
> On Tuesday, November 4, 2014 3:45:35 AM UTC+1, Taylor Lapeyre wrote:
>>
>>
>>
>> GitHub project link:
>> https://github.com/taylorlapeyre/oj
>>
>> The idea is to lay a solid foundation for talking to databases in Clojure
>> using regular Clojure data structures to represent queries. My goal is to
>> let this library become established enough that is becomes the foundation
>> for larger frameworks that abstract away the ideas found in SQL.
>>
>> Looking for feedback and for others to help me on this project! I hope
>> you find this useful, it has been very useful for me so far.
>>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
