This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-24
Channels
- # admin-announcements (2)
- # beginners (46)
- # boot (8)
- # cider (29)
- # cljs-dev (45)
- # cljsjs (10)
- # cljsrn (13)
- # clojure (60)
- # clojure-dev (5)
- # clojure-greece (1)
- # clojure-ireland (4)
- # clojure-mexico (6)
- # clojure-poland (3)
- # clojure-quebec (3)
- # clojure-russia (8)
- # clojure-spec (89)
- # clojure-uk (70)
- # clojurescript (84)
- # cursive (4)
- # datomic (7)
- # devcards (1)
- # dirac (2)
- # emacs (11)
- # hispano (10)
- # jobs (13)
- # keechma (34)
- # lein-figwheel (4)
- # luminus (19)
- # off-topic (2)
- # om (78)
- # onyx (6)
- # parinfer (1)
- # planck (82)
- # proton (2)
- # re-frame (10)
- # reagent (23)
- # ring-swagger (5)
- # spacemacs (2)
- # specter (24)
- # spirituality-ethics (122)
- # untangled (13)
@rauh datascript has an implementation that seems to agree with datomic:
boot.user=> (ds/squuid) (d/squuid)
#uuid "576cfc7a-f3e7-493c-bb6a-da9536ec6caf"
#uuid "576cfc7a-8671-4d59-8053-6be834ac295f"
@rauh also https://github.com/clojure-cookbook/clojure-cookbook/blob/master/01_primitive-data/1-24_uuids.asciidoc
@stuarthalloway: Thanks! Got it all working. 🙂 The java.util.UUID/randomUUID
also shows setting the variant nicely
Hi everyone. I wrote a blog post about the first steps to using property-based testing to test your Datomic transaction building code: http://blog.altometrics.com/2016/06/property-based-testing-with-clojure-and-datomic-part-2/ I’m interested in your thoughts on the approach.