You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really helpful for me, especially as a novice clojure user, to have a description of the differences between sqlingvo and the others sql libraries along with the motivation for creating sqlingvo.
I think the main libraries in this space are sqlingvo, honeysql, and korma. I'm sure there are others, but these seem to be the major libraries that support using clojure data structures to write SQL (unlike yesql and hugsql which support a SQL first approach).
The text was updated successfully, but these errors were encountered:
If you ever get a chance to look into honeysql, I'd be interested to hear your thoughts. As a novice clojure user, I'm finding the use of native clojure maps to describe a sql query pretty useful for the purposes of composition and learning very little to get started.
SQLLingvo works a lot like HoneySQL, but defines a slightly different-looking DSL and eschews the intermediary maps (actually, it does use maps if you try executing the functions alone, but they’re a lot less readable than HoneySQL’s). Instead, the base query functions (select etc.) can contain forms modifying the query, and it applies the transformations internally rather than externally as in honey.
I'd be curious what benefits you found by having an intermediary like sqlingvo.expr.Stmt while creating sqlingvo.
It would be really helpful for me, especially as a novice clojure user, to have a description of the differences between
sqlingvo
and the others sql libraries along with the motivation for creatingsqlingvo
.I think the main libraries in this space are
sqlingvo
,honeysql
, andkorma
. I'm sure there are others, but these seem to be the major libraries that support using clojure data structures to write SQL (unlike yesql and hugsql which support a SQL first approach).The text was updated successfully, but these errors were encountered: