honeysql-postgres

> I've found templated queries(e.g. yesql) are far preferable for complex selects/joins/subselects and just can't imagine using the data structure dsl for such queries I work with lots of CTEs, UNIONS, JOINS, and sub-selects and can't imagine not using data structures to validate individual parts of the query as I'm designing it. Particularly given how trivial it is in HoneySQL (anywhere a sub-select is legal you can insert a HoneySQL query map). Further, I use a lot of the jsonb and postgis features of Postgres and HoneySQL is a champ here. Not everything is supported out of the box[0], but adding any missing clause or operator is just a quick defmethod away. Between HoneySQL and clojure.java.jdbc, working with PostgreSQL's JSON support feels like Mongo with the added abilities of custom types, transactions, and function indexes. I do ha

I recently started using honeysql and so far it has been great. There is some learning curve figuring put how things work, but the advantages of having SQL encoded as clojure data are worth it, in my opinion: - s-expressions everywhere means that structural editing works - allows for easy composing of sql queries - can very easily add custom filters, joins, etc and build up queries dynamically - can easily add abstractions, for example something like https://github.com/metabase/toucan/blob/master/README.md If you use postgresql, check out: https://github.com/nilenso/honeysql-postgres/blob/master/REA...