This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-24
Channels
- # announcements (4)
- # asami (5)
- # babashka (20)
- # beginners (94)
- # bristol-clojurians (1)
- # calva (23)
- # cider (2)
- # clj-commons (3)
- # clj-kondo (43)
- # cljfx (2)
- # cljs-dev (13)
- # clojure (112)
- # clojure-dev (44)
- # clojure-europe (17)
- # clojure-nl (5)
- # clojure-poland (12)
- # clojure-spec (2)
- # clojure-uk (3)
- # clojurebridge (1)
- # clojurescript (92)
- # cursive (17)
- # data-science (8)
- # datahike (1)
- # datalevin (1)
- # datomic (3)
- # deps-new (7)
- # events (2)
- # fulcro (40)
- # graalvm (110)
- # holy-lambda (16)
- # introduce-yourself (1)
- # lsp (13)
- # malli (8)
- # missionary (12)
- # off-topic (10)
- # pathom (13)
- # polylith (10)
- # portal (28)
- # re-frame (37)
- # reitit (1)
- # releases (1)
- # shadow-cljs (30)
- # spacemacs (1)
- # tools-deps (9)
- # xtdb (10)
Hi, @quoll 🙂 Have you given any thought to supporting namespaced :id? E.g. having :person/id and :city/id. Would make sense (at least from a non-technical standpoint) and would help with differentiating different kinds of entities, just like other attributes such as :person/name. Maybe make a rule along the lines of "every attribute ending in /id is treated as :id"?
Probably don't need specific examples, but this would help with using entity with #fulcro, where namespaced id's play a prominent role. Currently I need to use rename-keys. It's a minor nuisance, to be sure :)
This doesn’t make sense from the DB perspective, but there’s no technical reason I can’t. I think I could manage it. Want to submit a ticket for me?
It could, yes. The only way to find these is to iterate through the keys. I do iterate through all key/values in an entity, but before I do I need to have knowledge of the node that represents that entity. The only approaches would be to iterate twice through every entity, or else backtrack over generated triples and rewrite them (which is probably more expensive).
Hm, I probably wouldn't make that trade-off for my example above, to be honest.
Also, the rule I had in mind above is starting to sound a bit like having a schema. If that rule, than why not also enforce uniqueness of the value of :person/id... Yes, not sure it's a good fit for the open world model.