This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-23
Channels
- # aws (3)
- # babashka (17)
- # beginners (44)
- # boot (1)
- # bristol-clojurians (1)
- # cider (19)
- # clj-kondo (7)
- # cljfx (5)
- # clojure (35)
- # clojure-australia (25)
- # clojure-europe (41)
- # clojure-nl (4)
- # clojure-spec (5)
- # clojure-uk (104)
- # clojuredesign-podcast (1)
- # clojurescript (41)
- # component (6)
- # conjure (5)
- # core-async (20)
- # core-logic (5)
- # cryogen (7)
- # cursive (4)
- # data-science (1)
- # datomic (14)
- # devcards (2)
- # events (1)
- # fulcro (6)
- # helix (6)
- # jobs (4)
- # kaocha (4)
- # lambdaisland (4)
- # leiningen (3)
- # luminus (1)
- # malli (2)
- # meander (2)
- # mount (6)
- # off-topic (2)
- # pedestal (25)
- # rdf (1)
- # re-frame (17)
- # reagent (5)
- # releases (1)
- # reveal (13)
- # rewrite-clj (45)
- # shadow-cljs (27)
- # sql (18)
- # tools-deps (93)
- # vim (13)
- # xtdb (11)
Our Datomic Cloud subcription is not showing up on the AWS Marketplace / Manage subscriptions https://console.aws.amazon.com/marketplace/home?region=ap-southeast-1#/subscriptions is that expected? I see other subscriptions though from Container / Machine Image and CloudFormation categories...
the analytics doesn’t seem to work if db-name contains a dash - character, I’m getting Query 20201123_062629_00002_8pm43 failed: Expected string for :db-name when trying a query, but it works if db name contains only characters
I had a test db that was named project-2020-11-13 with a date and it didn’t work but the db named just project worked fine
huh. for what it's worth, i'm running analytics on a db with a dash in its name without an issue
I have relation when order has customet attribute and can access customer via: [?o :order/customer ?c] The same way I can access order if I have query of customers. Also I can use get-else when order has no customer. But how can I filter customers without orders? (not [?o :order/customer ?c]) gives an error
:db.error/insufficient-binding [?o] not bound in not clause: (not-join [?o ?c] [?o :order/customer ?c])And also seems that not is a sugar on not-join, allowing not to set bindings explicitly and manually
@U0A6H3MFT it seems to me that issue lies entirely in the binding
[Cloud/Ions] Does all deps have to be under :deps, or can aliases be specified when pushing?
no, AFIK, you can specify an alias
As I dig (not documented or explained by anyone):
the datomic-cloud instance will download your code, open your deps.edn, take the :deps make and decide which deps it will use (something like, it do not use #tools-deps or at least, not as a simple command line)