This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-28
Channels
- # aws (7)
- # beginners (69)
- # boot (67)
- # cider (9)
- # cljs-dev (159)
- # cljsrn (2)
- # clojars (25)
- # clojure (345)
- # clojure-austin (9)
- # clojure-berlin (1)
- # clojure-dusseldorf (10)
- # clojure-italy (3)
- # clojure-nl (1)
- # clojure-portugal (1)
- # clojure-spec (73)
- # clojure-uk (59)
- # clojurescript (163)
- # clojurewerkz (1)
- # component (26)
- # core-matrix (2)
- # cursive (20)
- # datascript (32)
- # datomic (15)
- # dirac (16)
- # emacs (3)
- # hoplon (35)
- # jobs-discuss (87)
- # jobs-rus (95)
- # luminus (15)
- # om (135)
- # om-next (3)
- # onyx (47)
- # pedestal (67)
- # perun (74)
- # play-clj (4)
- # portland-or (1)
- # proton (4)
- # re-frame (13)
- # reagent (18)
- # remote-jobs (17)
- # rum (20)
- # specter (11)
- # untangled (101)
- # yada (18)
I can list all the attributes and their type in the database with this query: (d/q '[:find ?i ?t :where [?e :db/ident ?i] [?e :db/valueType ?t]] (d/db conn)) Is there a entity that I can "join in” to get the types in text instead of a number? I can of course add that as a source with hardcoded values, but if there is an entity for that already, then that’s better.
@marshall should I expect a memory leak if I hold on to a Log instance and perform repeated calls to .txRange()
?
in other words: can I rely on the tx ranges being garbage-collected even if I hold on to the Log ?
are datomic docs by any chance served from s3? http://docs.datomic.com/ down for me
http://isitdownorjust.me/docs-datomic-com/ confirms it's down.
yes, it's related to S3 issues.
I tried finding the answer to this in the docs and by searching, but had no luck. Why would this query
(take 2 (query '[:find (pull ?id [*]) :where [?id :account/name]]))
give me something like this?
([{:db/id …}] [{:db/id …}])
I would expect something like this:
({:db/id …} {:db/id …})