This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-08
Channels
- # aleph (52)
- # beginners (74)
- # boot (8)
- # cider (4)
- # clara (3)
- # cljs-dev (1)
- # cljsjs (2)
- # cljsrn (1)
- # clojars (2)
- # clojure (300)
- # clojure-argentina (1)
- # clojure-dev (9)
- # clojure-italy (10)
- # clojure-nl (1)
- # clojure-russia (77)
- # clojure-sg (9)
- # clojure-spec (38)
- # clojure-uk (70)
- # clojurescript (108)
- # core-async (12)
- # cursive (9)
- # data-science (4)
- # datascript (7)
- # datomic (37)
- # defnpodcast (4)
- # emacs (11)
- # graphql (6)
- # jobs (3)
- # jobs-discuss (1)
- # juxt (3)
- # keechma (1)
- # klipse (4)
- # lein-figwheel (1)
- # lumo (1)
- # off-topic (3)
- # om (5)
- # onyx (10)
- # parinfer (3)
- # pedestal (1)
- # perun (1)
- # protorepl (3)
- # re-frame (35)
- # reagent (19)
- # spacemacs (4)
- # specter (2)
- # uncomplicate (279)
- # unrepl (32)
@devth you can't change :db/valueType
http://docs.datomic.com/schema.html#sec-5-3
I see somewhere, but not recommended: "If you really need to alter valueType, rename the attribute to a new ident, then create a new one with correct type"
does anyone use conformity? https://github.com/rkneufeld/conformity I have a question about it's purpose:
In a more general sense, conformity allows you to declare expectations (in the form of norms) about the state of your database, and enforce those idempotently without repeatedly transacting schema, required data, etc.
Is there any harm in repeatedly transacting the schema? Isn't that operation already idempotent?when you have a big schema, is good to know all old migrations before do a new one. (yes, you can do it with git history, transaction log... but plain text is a good way 😉 )
technically yes, but any transaction has side effects, even if they may be negligible or acceptable
i haven’t tested the ultimate effects, but you will leave a swath of extra transaction datoms behind if you just run your schema file on startup
it may also be true that some forms of schema migrations could be destructive and should never be repeated, although i have none of that type
maybe something like “ensure that this schema has exactly six entities with :user/admin
” or something similarly contrived that you may not always want to be true, but may wish to ensure that a db starts with?
@pbostrom shameless plug: you may want to check out the README of datofu (https://github.com/vvvvalvalval/datofu#managing-data-schema-evolutions) for a guide on migrations. HTH, feedback welcome
The internals are essentially the same as conformity
Hi all, trying to start up the console but I am getting: java.lang.IncompatibleClassChangeError
. Any ideas? Using the demo pro version. The transactor is running System started datomic:
@aramz Are you using datomic FREE? There is a known issue with Datomic FREE and console. We’re working on a fix. If you register for Datomic starter (which is free to use) the Datomic PRO edition has no classpath issue with using console.
as per the console readme, I’ve tried both: bin/console -p 8080 alias transactor-uri-no-db
and bin/console -p 8080 mbrainz datomic:
does the pro already come with the console? I downloaded the console separately and ran the install-console
@uwo maybe connect to the transactor then kill it :p