This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-19
Channels
- # admin-announcements (2)
- # aws-lambda (3)
- # beginners (66)
- # boot (61)
- # cider (1)
- # cljs-dev (17)
- # clojure (100)
- # clojure-austin (4)
- # clojure-brasil (1)
- # clojure-canada (8)
- # clojure-quebec (6)
- # clojure-russia (48)
- # clojure-sg (6)
- # clojure-spec (37)
- # clojure-uk (61)
- # clojure-ukraine (2)
- # clojurescript (80)
- # core-async (13)
- # cursive (20)
- # datascript (37)
- # datomic (2)
- # defnpodcast (4)
- # emacs (5)
- # funcool (3)
- # hoplon (11)
- # jobs (7)
- # juxt (26)
- # lein-figwheel (48)
- # leiningen (3)
- # luminus (3)
- # om (34)
- # om-next (5)
- # onyx (5)
- # protorepl (6)
- # re-frame (10)
- # reagent (9)
- # rethinkdb (16)
- # ring-swagger (5)
- # spacemacs (14)
- # specter (54)
- # untangled (36)
- # vim (75)
- # yada (1)
I had opened the GH issue the other day regarding us trying to inspect a rethink query before it's sent to rethink
You had mentioned rethinkdb.query-builder/parse-term
which gives us, well, this....
So, I mean, correct me if I'm wrong, but this can't be what's literally sent over the wire to Rethink? My limited understanding was that the output should look something like what you might type into the RethinkDB browser query tool? (E.G. http://puu.sh/q71aE/9ba077ca4d.png)
this is what's actually being sent, only converted to a json string. you can read more about it here: https://rethinkdb.com/docs/writing-drivers/#serializing-queries. is it a complicated query? 5,500 lines seems a bit crazy unless it includes data being inserted.
I guess what we did was locked a junior dev in a closet for 6 months to write all of our queries
annddd now we're trying to make sense of it (and trying to make sense of how one of these queries is 5,500 lines...) lol
Sometimes just rewriting a component is saner than figuring out itโs inner workings