Anyone have an example of a moderately complex (i.e. more than a toy but not a massively intertwingled app) use of HoneySQL?

i feel a bit like i am wandering around in the dark

Not that’s open source, sadly, but I’m happy to share my experiences / opinions if that’s at all helpful

At this point I don’t have a lot of specific questions rather a general sense that I don’t have a good mental model for how to think about managing persistent data via something like HoneySql when I get into more complex associations and I’d like to see a few examples I can work from.

but thank you for the offer, if I do have some specific scenarios or questions I will bring them

it largely depends on your use case. We have a few tables that are conditionally joined and make multiple uses of some tables (such that we often need different where clauses, and we don't know the exact query ahead of time)

sandbags: if you find yourself doing this: http://emidln.com/honeysql-talk/#/10

you probably want honeysql

@bja: i’m already using honeysql, but as i stray into managing the associations i’m looking at whether there is already a best practice

i’ve thrown out using records for entities

as it seems to make joined data unnecessarily complicated

I don't know if there is a best practice, but I find that cond-> results in easy to understand code

a lot of times we'll have something like (defnk find-domain-object ...) where optional parameters might build a set of various correlated subqueries

defnk?

yeah i’ve built some stuff for creating obvious queries around a “model definition” map

i guess i will just muddle along and see what i come up with, i was just hoping to short-circuit that process

unfortunately i have very little time for dev stuff which makes progress difficult right now

plumbing.core/defnk

we tend to use that for query builder definitions as there are a ton of parameters and we'd like the runtime assertions

(sorry for that, wrong window)