This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-03
Channels
- # beginners (111)
- # boot (1)
- # braveandtrue (4)
- # calva (2)
- # cider (16)
- # clara (35)
- # cljdoc (4)
- # cljs-dev (22)
- # clojure (80)
- # clojure-dev (17)
- # clojure-europe (3)
- # clojure-italy (57)
- # clojure-japan (1)
- # clojure-nl (4)
- # clojure-serbia (1)
- # clojure-spec (25)
- # clojure-uk (108)
- # clojurescript (67)
- # cursive (17)
- # data-science (5)
- # datascript (6)
- # datomic (6)
- # devcards (1)
- # events (1)
- # expound (13)
- # figwheel (2)
- # figwheel-main (6)
- # fulcro (7)
- # jobs-discuss (8)
- # kaocha (1)
- # luminus (3)
- # nrepl (6)
- # off-topic (58)
- # re-frame (1)
- # reitit (16)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (70)
- # spacemacs (10)
- # sql (42)
- # testing (1)
- # tools-deps (8)
- # vim (1)
@kenny Are you using deps.edn
?
I probably ought to cut 0.9.5 of HoneySQL sometime soon... the change list is building up https://github.com/jkk/honeysql/compare/v0.9.4...master
Is there a way for query to return a map where the keys are sorted in the order the select statement had them?
@didibus No. You could do it in next.jdbc
by writing your own ResultSetBuilder
.
(sorry, I was off having dinner and didn't see the question until now)
Eh no worries, I had paid commercial support that wasn't this fast so not complaining one bit 😋
Happy to walk you through how to do it with next.jdbc
. I want to get folks moved to that anyway.
Its okay, I'm too committed to clojure.java.jdbc now 🤤. Also, realized the order should probably be defined in the view anyways.
I know your team likes to be cutting edge on dependencies, but mine it's the other way around hehe
next.jdbc
is the next version of clojure.java.jdbc
🙂
We're using it at work.
It is, technically, alpha right now, but I am aggressively aiming for a 1.0.0 release.
clojure.java.jdbc
is 0.7.9 right now and probably won't get another release at this point, unless there are critical bugs that need fixing.
OK. The API is stable. The only changes have been in esoteric stuff that @ikitommi wanted.
Mostly because it's a huge pain to import dependencies internally at my work. So I prefer bringing in version that aren't seeing a lot of activity 😋
Ah, interesting. OK, fair enough.
I don't know. Maybe I'll give it a quick look if I find some time and see if I can sneak it in. But ya, we can't depend directly on Clojars or Maven. So any external lib I import is just a huge hassle. Goes through license review by legal team and quick security check of the source
Ouch!
The license is EPL 1.0, like Contrib/Clojure. Deliberately.
I'd certainly appreciate a security check of the source so... hey, if you could get those wheels rolling, that would be beneficial 🙂
Oh... that's... very corporate 😐
I'm kind of amazed you've managed to get Clojure in at all...
Anyways, I'm still looking forward to next.jdbc. it looks really nice. I'll eventually get around to using it
When I interview with a company, I always make sure they understand that I contribute to OSS, I intend to continue contributing to OSS, and that I will expect at least some work done at/for the company to be OSS.
I've had it written into employment contracts.
Years ago (ahem, decades ago), I worked for a firm of actuaries where we couldn't install anything on our machines. When support came to install something on my colleague's machine next to me, I had already put in a ticket for the same software and suggested that they pass the disks to me and we install it on both machines at the same time. Nope. They put each disk back into their secure briefcase as they used it, and they would come out later to install the same software on my machine. Argh! I lasted five months.