This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-31
Channels
- # admin-announcements (4)
- # alda (3)
- # aws (1)
- # beginners (2)
- # boot (33)
- # braid-chat (4)
- # braveandtrue (20)
- # cider (52)
- # cljs-dev (13)
- # cljsrn (55)
- # clojure (111)
- # clojure-belgium (4)
- # clojure-brasil (6)
- # clojure-dusseldorf (1)
- # clojure-greece (116)
- # clojure-mexico (1)
- # clojure-nl (3)
- # clojure-russia (56)
- # clojure-spec (72)
- # clojure-uk (13)
- # clojurescript (66)
- # community-development (2)
- # component (24)
- # core-async (1)
- # cursive (19)
- # datomic (27)
- # devcards (5)
- # emacs (1)
- # funcool (34)
- # hoplon (313)
- # jobs (1)
- # lein-figwheel (11)
- # luminus (5)
- # mount (30)
- # off-topic (63)
- # om (375)
- # onyx (67)
- # perun (8)
- # proton (1)
- # reagent (4)
- # rum (1)
- # specter (55)
- # spirituality-ethics (7)
- # test-check (2)
- # untangled (34)
- # yada (20)
We’re using Datomic with a DynamoDB back-end, I was just looking at AWS Quicksight, and I imagine that even though we’re using DynamoDB as the store I imagine we would’t be able to just transact directly from DynamoDb into QuickSight because Datomic would obfuscate the data in Dynamo somehow. Is that correct?
xsyn: That's accurate. DynamoDB is just the backing store. The data itself is encoded by Datomic.
I've started on spec
-ing Datomic queries: https://gist.github.com/nwjsmith/0b87c522cfeba68f1928d48c89adef78
i wonder if Cognitect will be doing the same officially
query generators is a fascinating idea 🙂
@robert-stuttaford: yeah, would be cool
I'm impressed with how easy it is to translate the grammar from http://docs.datomic.com/query.html#grammar to spec
.
My goal here is to be able to test.check
some query-generating code I'm going to write
No promises about the future. 🙂 Though the generic background context is - as with most companies -Cognitect designs and ships things that solve problems we have or our customers have.
You can typically assume that Datomic will take advantage of new Clojure language features (with Clojure version adoption lag) and that Datomic itself will, from time to time, motivate new language features in Clojure.
@bkamphaus: Can you elaborate on the specific problems that drove you to spec?
@potetm: The motivations for clojure.spec are described in the guide http://clojure.org/about/spec
Yeah I was curious whether there were specific projects you guys had that pushed this to the fore.
(I know there's only so much you can/will divulge. I was just curious, so I thought I'd ask.)
Datomic 0.9.5372 is now available https://groups.google.com/d/msg/datomic/sF5C5mpLCmE/gq29iOxpAgAJ
Is it true that transactions should not have more than one million datoms in them?
@currentoor: “should not have” is a pretty strong phasing, but it’s likely that transactions of that size are likely to run into performance issues (best performance size is ~40k or so) — do you have transactions of that size that represent an atomic boundary in the domain?
@bkamphaus: not in the domain, I just need to migrate some old data
so this script will just run once and not be userfacing
@currentoor: if its not atomic in the domain I would break it up into smaller transactions and pipeline it, as per the example here: http://docs.datomic.com/best-practices.html#pipeline-transactions
@bkamphaus: thanks I'll check it out.