Are you using the same namespaces? That might cause problems for people if they accidentally get both versions on the classpath.

(as can happen if you, for example, bring in a library which builds atop crux)

Hey @U09LZR36F 👋 For our mirrored dependencies, no - they've been run via mranderson; for Crux, yes, on the assumption that having multiple dependencies on Crux within one application is sufficiently uncommon, and that people who do are already aware of it. Obviously keen to hear of any cases where this may cause issues 🙂

When using maven, this can happen accidentally unfortunately.

It's usually a very frustrating few days of pain trying to get to the bottom of something then realising you have both juxt/crux-core and pro.juxt.crux/crux-core on the classpath.

https://github.com/clojars/clojars-web/issues/801 maven has relocation to support this, which is currently WIP on Clojars.

Thanks for the relocation pointer - will include this when we next deploy to Clojars in anticipation of that feature becoming available 🙏

Indeed - have had a few of those days myself...

Often (IME, at least) they're with libraries much deeper in the dependency tree, referred to by multiple other libraries (the dependency diamond). Our assumption is that Crux is rarely (if ever?) a transitive dependency - rather, a direct dependency of the final end-user application - as I say, though, keen to hear of examples to the contrary 🙂

https://github.com/teknql/crux-geo/blob/main/deps.edn almost an example 😛 but not quite. https://clojars.org/io.kosong.crux/crux-hbase though, and https://clojars.org/net.clojars.roterski/fulcro-rad-crux

Not in exactly the same way, since there's no upfront schema and it uses explicit IDs, but it certainly does allow you to traverse the graph - thanks to duck-typing of triple clause reference lookups purely at query time / "schema on read"

hmm, but what constitutes a “pointer” from one document to another?

anything basically. I usually use UUIDs or maps. e.g. if you have two docs in the db like this:

{:crux.db/id #uuid "abc..."
 :foo/bar #uuid "123"}
{:crux.db/id #uuid "123..."
 :msg/text "hello"}

:where '[[doc-a :foo/bar doc-b]
         [doc-b :msg/text text]]

same thing goes for pull and crux.api/entity -- if you put something where a document ID is supposed to go, Crux will happily treat it as a document ID

@U7YNGKDHA that’s very flexible and convenient, many thanks for the explanation!