This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-15
Channels
- # architecture (5)
- # babashka (34)
- # beginners (72)
- # calva (42)
- # cherry (31)
- # cider (14)
- # clojure (27)
- # clojure-europe (11)
- # clojure-norway (17)
- # clojure-uk (1)
- # clojurescript (25)
- # community-development (13)
- # conjure (1)
- # core-async (11)
- # datascript (18)
- # datomic (11)
- # emacs (12)
- # fulcro (10)
- # integrant (5)
- # introduce-yourself (3)
- # jobs (8)
- # juxt (2)
- # malli (22)
- # off-topic (11)
- # pathom (18)
- # polylith (62)
- # rdf (18)
- # reagent (8)
- # releases (1)
- # shadow-cljs (35)
- # sql (3)
- # squint (141)
- # tools-deps (12)
- # vim (4)
- # xtdb (4)
has any work been done to make Datomic on-prem's metrics and logging compatible with OpenTelemetry? we would love to use http://Honeycomb.io but not having the database in the picture is a pretty big blocker ๐
I think of an index as a way group a set of things by some property, given a uuid is about randomness, it's unclear to me when a https://docs.datomic.com/on-prem/schema/identity.html#squuids aka a uuid with an ordered time component, would be useful. except for a general query against all such uuids? like give me everything in the db from the last week? It's really indexed by just the time aspect right?
new values accumulate on the โtailโ of the tree vs randomly distributed throughout the entire tree
So it will improve performance in general query cases, not just the time based one i was thinking of?
it will reduce the amount of garbage segments the transactor produces when it makes an index, and may make preparing the new indexes faster also.
What type is a db/id? can it be a long id? i'm trying to make sense of this https://github.com/tonsky/datascript/issues/292 about datascript, i'm not sure that they mean and i'm worried im missing something. by jvm do they mean datomic? why would the jvm have any say on anything "id" related? > It seems that long ids are no longer supported on JVM since 0.18.0. I also added a validation that throws on both JVM and JS if value is out of range.
The comment means that datascript rejects entity ids in the long range (specifically > 0x7FFFFFFF)
it rejects them on the JVM even though they would be fine, because they would not be fine on js/cljs
yep, that makes sense and mirrors what i'm seeing on my end to. datomic says an eid should be a nat-int? and that seems to include the eids that are causing exceptions in datascript. Thanks for the help :thumbsup: