This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-17
Channels
- # adventofcode (3)
- # announcements (1)
- # babashka (25)
- # beginners (55)
- # calva (12)
- # cider (40)
- # clj-kondo (13)
- # clojure-australia (2)
- # clojure-dev (11)
- # clojure-europe (67)
- # clojure-france (6)
- # clojure-nl (16)
- # clojure-uk (9)
- # clojuredesign-podcast (9)
- # clojurescript (17)
- # conjure (7)
- # cursive (3)
- # datomic (3)
- # emacs (8)
- # figwheel-main (7)
- # fulcro (21)
- # google-cloud (21)
- # graphql (8)
- # helix (1)
- # honeysql (32)
- # instaparse (2)
- # jobs (2)
- # jobs-discuss (2)
- # meander (80)
- # mount (1)
- # off-topic (25)
- # pathom (31)
- # polylith (1)
- # rdf (24)
- # re-frame (21)
- # reagent (29)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (16)
- # slack-help (6)
- # sql (5)
- # tools-deps (23)
- # uncomplicate (2)
- # wasm (2)
- # xtdb (4)
collisions aside, are there any indexing and/or query performance benefits of using a uuid
vs a string
as some entity identifier? for example
{:player/id #uuid"cb7afbf9-95ca-4c5b-af42-b096342bae61"}
vs
{:player/id "a4st390xrvskm9ecm452jbn"}
I asked a similar question, https://github.com/zelark/nano-id/issues/12#issuecomment-625522643 The answer appears to be that there's not much of a difference, https://clojurians-log.clojureverse.org/datomic/2020-05-08/1588924450.320800 (currently getting a gateway timeout error)
that's perfect, thanks @U0P7ZBZCK. go figure, i prefer UUIDs but i have to incorporate some string ids coming from a non-Datomic system. :man-shrugging:
👍 3