honeysql

Discussion of https://github.com/seancorfield/honeysql :slightly_smiling_face:
dharrigan 2019-09-06T07:36:01.007600Z

I think I will continue here

dharrigan 2019-09-06T07:36:07.007800Z

I do like the proposal for "https://github.com/jkk/honeysql/issues/247"

dharrigan 2019-09-06T07:36:13.008200Z

esp as it's the "modern" age 🙂

seancorfield 2019-09-06T07:37:20.008900Z

Yeah, I need to get Jon Doane's input on that since he submitted the PR that essentially broke this behavior several years ago...

seancorfield 2019-09-06T07:38:59.010300Z

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.

seancorfield 2019-09-06T07:39:41.011100Z

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...

seancorfield 2019-09-06T07:41:57.011500Z

All the dynamic vars bug me as well...

dharrigan 2019-09-06T07:46:09.011900Z

raw stuff has helped me, for example for postgis

dharrigan 2019-09-06T07:46:25.012300Z

I construct the functions to use directly in sql and just use them "raw"

dharrigan 2019-09-06T07:47:07.012600Z

perhaps I should look to write a "postgis" extension to honeysql 🙂

grierson 2019-09-06T09:48:14.013300Z

Is there a way that I can refactor this query to make it more concise?