I think I will continue here
I do like the proposal for "https://github.com/jkk/honeysql/issues/247"
esp as it's the "modern" age 🙂
Yeah, I need to get Jon Doane's input on that since he submitted the PR that essentially broke this behavior several years ago...
There's actually a lot that kind of annoys me about HoneySQL so I'm contemplating a new set of namespaces with some rather streamlined behavior... I just haven't figured out whether I want to just modify aspects of the current library or build a new implementation from scratch.
The raw/inline stuff just drives me bonkers. And there's some rough edges around DB-specific syntax issues that there's no good resolution for...
All the dynamic vars bug me as well...
raw stuff has helped me, for example for postgis
I construct the functions to use directly in sql and just use them "raw"
perhaps I should look to write a "postgis" extension to honeysql 🙂
Is there a way that I can refactor this query to make it more concise?