This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-05
Channels
- # admin-announcements (8)
- # beginners (73)
- # boot (14)
- # cljsrn (4)
- # clojure (157)
- # clojure-indonesia (1)
- # clojure-poland (1)
- # clojure-russia (3)
- # clojurecup (32)
- # clojurescript (123)
- # clojurex (4)
- # core-async (8)
- # cursive (7)
- # datavis (26)
- # datomic (5)
- # hoplon (2)
- # off-topic (3)
- # om (41)
- # portland-or (6)
- # random (1)
- # re-frame (11)
- # slack-help (3)
- # specter (1)
can anyone point me at any transaction functions that use require or are more than one line examples? Struggling with google for this 😕
https://github.com/Datomic/day-of-datomic/blob/master/tutorial/transaction_function_exceptions.clj
Is it considered an anti-pattern if a database transaction function can only produce consistent results if it runs in a transaction all by itself?
E.g. running :do/thing
twice in one transaction on parameters that aren't independent like so: (d/transact conn [[:do/thing x y z] [:do/thing x y p q]])
would, due to the implementation details, yield bad results.
So instead we have to run that as two separate transactions:
(d/transact conn [[:do/thing x y z]])
(d/transact conn [[:do/thing x y p q]])