This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (4)
- # aws (1)
- # beginners (60)
- # calva (10)
- # cider (21)
- # clj-kondo (38)
- # cljdoc (1)
- # clojure (59)
- # clojure-austin (1)
- # clojure-conj (1)
- # clojure-europe (19)
- # clojure-italy (9)
- # clojure-nl (29)
- # clojure-spec (6)
- # clojure-uk (85)
- # clojurescript (54)
- # community-development (11)
- # core-async (2)
- # cursive (21)
- # data-science (4)
- # datomic (39)
- # events (2)
- # fulcro (48)
- # funcool (1)
- # graalvm (5)
- # jackdaw (9)
- # kaocha (17)
- # luminus (2)
- # off-topic (10)
- # parinfer (22)
- # quil (1)
- # re-frame (4)
- # reagent (29)
- # shadow-cljs (7)
- # sql (9)
- # tools-deps (31)
- # yada (1)
what happened to
:db.type/bytes? is there a similar type in Datomic Cloud for storing a map, or other data that doesn't fit into the other valueTypes?
@wei If it's big, use a reference in s3, if not, you can Base64 encode/decode either the
pr-str of a datastructure or even the binary representation. Example would be a fressian encoded vector could then be Base64 encoded into a string. The tricky part is knowing if somehow you would overflow the string size limit of ~4000 characters. Hence the first recommendation of using s3.
I'm not speaking authoritatively about what happened to
:db.type/bytes, just sharing some ideas i've had around working around their absence.
for the impatient https://www.youtube.com/watch?v=jVKGYu0_OCA
congratulations on shipping! this was my #1 feature request for a while and I'm thrilled that you guys have pulled it off. would be fun to hear about the challenges you encountered implementing this.
Is it supposed to work with AWS Athena as well? I didn't see a mention in the docs, but that should be similar to Presto
there isn’t a path from Athena to ROYB presto, and QuickSight requires LDAP, so neither supported as of yet
Makes sense. Thanks for explaining
The new release is exciting, hoping to get some help with a chicken / egg problem. I would like to experiment with Datomic again (originally downloaded starter edition years ago), but it looks like my copy is limited to Datomic as of 2016. It seems like if I want to make software on my workstation and then make a pitch as to why we should buy it (or use AWS hosted etc once proven), I am stuck either getting full buy-in / budget up front, or trying to develop on my systems and never reboot so I can save my data in-between sessions via Datomic Free. Could someone help me understand if this is accurate, or if I am just misunderstanding the workflow?
Datomic Free is durable and survives reboots...
Or running Cloud (Solo) is ~$1/day (if you leave it on all the time)
I'm a happy user of Datomic Pro, but I wonder if Datomic Free would run nicely in a distributed fashion with https://aws.amazon.com/efs/
@U072WS7PE datomic-free still in
We can't use/learn/develop foss tools around
:keys or any of these new datomic features (as SQL connector)
You can request new entity ids by specifying a temporary id (tempid) in transaction data. The Peer.tempid method creates a new tempid, and the Peer.resolveTempid method can be used to interrogate a transaction return value for the actual id assigned.
Squuids are no longer required in Datomic (Cloud or On-Prem) now that Datomic has Adaptive Indexing.
It is often important to have a globally unique identifier for an entity. Where such identifiers do not already exist in the domain, you can use a unique identity attribute with a value type of :db.type/uuid.
https://docs.datomic.com/cloud/transactions/transaction-processing.html @meowlicious99 I know you're doing on-prem and not cloud, but that ^ is a useful reference for how transactions work
That’s how I always recognize it ^^