This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-16
Channels
- # aleph (2)
- # announcements (1)
- # beginners (162)
- # calva (16)
- # cider (37)
- # cljdoc (9)
- # cljs-dev (2)
- # cljsrn (3)
- # clojure (86)
- # clojure-dev (17)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-spec (10)
- # clojure-uk (20)
- # clojuredesign-podcast (15)
- # clojurescript (7)
- # data-science (14)
- # datascript (1)
- # datomic (5)
- # emacs (8)
- # figwheel-main (8)
- # fulcro (25)
- # graalvm (1)
- # jobs (10)
- # jobs-discuss (4)
- # keechma (14)
- # leiningen (2)
- # off-topic (31)
- # onyx (1)
- # other-languages (4)
- # pathom (4)
- # pedestal (1)
- # re-frame (20)
- # remote-jobs (4)
- # shadow-cljs (25)
- # sql (6)
- # tools-deps (15)
- # vim (18)
- # xtdb (9)
@seancorfield Hi Sean, have you seen anyone using next-jdbc
with Neo4j?
Not that I know of. I didn't even know neo4j had a JDBC driver...?
Ah, I guess it has had one for about three years @benisrood!
With the JDBC driver on your classpath, you ought to be able to use a db-spec of
{:dbtype "neo4j:bolt" :classname "org.neo4j.jdbc.bolt.BoltDriver" :dbname "..." ...}
(or use one of the other protocols/classes).You could probably just use :classname "org.neo4j.jdbc.Driver"
with any of the protocols, now I look at the source code... with :dbtype "neo4j:bolt"
or "neo4j:bolt+routing"
or "neo4j:http"
-- LMK if you try it and run into any issues.