This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-03
Channels
- # aleph (1)
- # announcements (9)
- # babashka (3)
- # beginners (200)
- # calva (22)
- # cider (74)
- # clojure (97)
- # clojure-dev (43)
- # clojure-europe (15)
- # clojure-italy (4)
- # clojure-nl (4)
- # clojure-sanfrancisco (2)
- # clojure-uk (103)
- # clojuredesign-podcast (2)
- # clojurescript (45)
- # core-async (5)
- # cursive (13)
- # datomic (42)
- # emacs (20)
- # fulcro (6)
- # graalvm (37)
- # jackdaw (10)
- # leiningen (7)
- # mid-cities-meetup (3)
- # off-topic (2)
- # pathom (1)
- # pedestal (3)
- # re-frame (6)
- # reagent (38)
- # reitit (5)
- # shadow-cljs (117)
- # spacemacs (1)
- # sql (1)
- # tools-deps (17)
- # vim (14)
- # xtdb (18)
Hi everyone
i just know about Crux, is it supposed to be a free alternative to Datomic?
there is something i'm thinking about i would like to share here with the developers of Crux, is it possible to add sparql engine to execute sparql queries?
i guess that will be a good win for Crux
the short answer is that 'Crux is an open-source, bitemporal, unbundled database that you can query using Datalog syntax' 🙂 'bitemporal' because you've got the option to edit the past as and when new information becomes available - you can ask both 'what do we know about the status of <x> at the start of the year?' (including later updates) and 'what did we know about <x> at that time?' (excluding updates, for audit purposes) 'unbundled' because we give users the choice of what underlying technologies to use - the transaction log, for example, can live on Kafka, in a JDBC database, or in memory; the indices can live in RocksDB or other kv-stores - we take advantage of their performance and reliability characteristics. best to have a look at the architecture diagram on https://github.com/juxt/crux#unbundled-architecture for this one re SPARQL - we do have some alpha-level support for SPARQL queries in the crux-rdf module, which translates a subset of SPARQL into Crux's datalog - would be interested to hear your ideas 🙂
@jarohen that's awesome
for definition of bitemporal you mean i can use it as timeseries db ?
at the moment we support point-in-time queries, but we're looking into how best to extend this to timeseries queries
so i can only save the value with only one point-in-time ?
you can get the history of a single entity through time, certainly - what we don't yet support is being able to see the results of a query through time (without querying at each individual point in time)
what is possible here is : x is_a 2 at 1/1/2020 x is_a 3 at 2/1/2020 x is_a 4 at 3/1/2020
subject is x , predicate is is_a, and the object is the multiple values so what i can achieve is save multiple values of object in time
is that possible ?
but only one object value should be active, and all other will be defined as history values of x in time
@jarohen thank you so much 🙂