This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-26
Channels
- # 100-days-of-code (3)
- # announcements (2)
- # beginners (237)
- # bitcoin (2)
- # boot (5)
- # cider (15)
- # cljs-dev (9)
- # cljsrn (6)
- # clojure (75)
- # clojure-estonia (1)
- # clojure-italy (8)
- # clojure-losangeles (1)
- # clojure-nl (1)
- # clojure-spec (68)
- # clojure-uk (80)
- # clojurescript (89)
- # cursive (31)
- # datomic (22)
- # emacs (2)
- # events (3)
- # figwheel-main (184)
- # fulcro (28)
- # graphql (1)
- # hyperfiddle (2)
- # jobs (1)
- # jobs-discuss (64)
- # luminus (5)
- # off-topic (16)
- # om (2)
- # onyx (1)
- # pedestal (12)
- # portkey (1)
- # re-frame (13)
- # reagent (56)
- # reitit (13)
- # ring-swagger (13)
- # shadow-cljs (145)
- # slack-help (2)
- # specter (6)
This is a thing that may help https://github.com/brandonbloom/backtick/blob/master/README.md
before i continue down the road of a custom migration tool, does Cognitect ever plan on supporting a feature to copy/clone a Datomic Cloud database?
Well, even if they do, could you wait until the arbitrary point in time when it is released?
@U0GC1C09L maybe an adaptation of this would work for you ? https://gist.github.com/vvvvalvalval/6e1888995fe1a90722818eefae49beaf
thanks @U06GS6P1N. i guess i'm just curious if copying/cloning a database will ever be a cloud supported feature 🙂
There's a feature request app you could check. Try this page then clicking on the 'feature request' button. https://www.datomic.com/support.html
If you want to just copy/clone (not do a migration), isn’t the implementation basically just: 1. Create new DB with the same schema, 2. Write a loop that sources data from one and transacts it to the other.
Hi, i'm trying to upgrade a Cloud 402, system to the latest version, and follwing the 'first upgrade ever' instructions. The stack deletion failed because it looks like the TxGroupRole still has policies attached. Is it ok to fix this by hand? and retry the deletion?
Solved, the problem, looks like the delete is only pulling off the policies that were added via the stack creation, the policies i added by hand were gumming up the works. Might be a useful FYI for the docs, and.or perhaps a future rev can grab the full list of policies and remove them
Thanks! I didn’t think of that. I’ll add it to the first upgrade docs. It shouldn’t be a problem for upgrades after that point
quick question, I'd like to match an attribute's value if it exists, and nil if it doesn't. Tried or'ing my clause with a missing
but that makes datalog frown lol because of the var mismatch. or-join doesn't help as I need the value
(or [?o :otuabund/accepted ?a]
[(missing? $ ?o :otuabund/accepted )])
I've a query aggregate function that looks at the collection of these and returns a value based on if they say they're all true, false, mixed, or 'missing'ah, that's simple. in the meantime, i realized it was better modeled with enums anyway , but will keep that in my back pocket