This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-27
Channels
- # adventofcode (3)
- # aws (1)
- # beginners (79)
- # boot-dev (1)
- # clara (50)
- # cljs-dev (7)
- # clojure (60)
- # clojure-austin (1)
- # clojure-germany (1)
- # clojure-greece (1)
- # clojure-russia (3)
- # clojure-spec (43)
- # clojure-uk (1)
- # clojurescript (76)
- # data-science (1)
- # datomic (26)
- # docs (2)
- # emacs (7)
- # fulcro (10)
- # hoplon (1)
- # instaparse (1)
- # lumo (3)
- # off-topic (16)
- # om (3)
- # onyx (2)
- # re-frame (3)
- # reagent (24)
- # ring-swagger (10)
- # shadow-cljs (15)
- # spacemacs (1)
- # sql (16)
- # uncomplicate (12)
- # unrepl (47)
Does anyone know how datomic handles repeated :db/add
transactions on an attribute that is cardinality one
.
but you can't :db/add twice in the same transaction, that will produce a datom conflict
gotcha. See thats what I thought too, but then I did a index query for datoms with that attribute that had been retracted (using .added
) and it found nothing
Say, are the datomic client libraries available on clojars or anywhere? Trying to write a little open-source datomic utility and I’m not sure what I should tell users about what to do about the libraries
I suppose I’ll just instruct them to use bin/maven-install from the datomic distribution, that seems simple enough
instructions are at the top of your datomic account page: https://my.datomic.com/account
Hi I was wondering something. How do I commit to datomic elements with cardinality many?
iterate over them and commit them one by one? o.o
maybe this is where my procedural software brain still doesn't grok FP
in my case users can provide a comma separated list of tags, i want to commit them all to the same "blurb" entity in the db. but a commit I can only do one element right? i want to commit many independent tags (with contributing user id) as cardinality many so I can keep track of who submitted which tag (and award verification/participation points)
hopefully my question makes sense. i am still kinda puzzled by how to resolve temporary IDs if I were to do a commit for the blurb contents and stuff and then subsequent commit for tag/val and tag/author and tag/blurb
that is a simple statement and helps.
more study required on my part
does that mean i can transact a vector and search against the set? that's what i want to do essentially
@U3ES97LAC it would probably be easier for us to help if you gave us a sample schema and expected query results :)