This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-29
Channels
- # architecture (2)
- # bangalore-clj (2)
- # beginners (177)
- # boot (1)
- # cider (36)
- # clara (15)
- # cljs-dev (30)
- # cljs-experience (6)
- # cljsrn (7)
- # clojure (94)
- # clojure-argentina (2)
- # clojure-brasil (1)
- # clojure-dusseldorf (6)
- # clojure-greece (1)
- # clojure-italy (18)
- # clojure-norway (4)
- # clojure-quebec (1)
- # clojure-russia (28)
- # clojure-sg (3)
- # clojure-spec (12)
- # clojure-turkiye (1)
- # clojure-uk (12)
- # clojurescript (169)
- # code-reviews (4)
- # community-development (2)
- # core-async (6)
- # core-matrix (6)
- # cursive (35)
- # datomic (18)
- # devcards (4)
- # euroclojure (1)
- # hoplon (2)
- # keechma (4)
- # klipse (2)
- # leiningen (1)
- # luminus (16)
- # mount (1)
- # off-topic (34)
- # om (31)
- # pedestal (6)
- # re-frame (14)
- # reagent (33)
- # specter (4)
- # uncomplicate (8)
- # unrepl (15)
- # untangled (24)
- # yada (25)
Hi! It is such a major pain to find any documentation on Datomic Free. I'm just trying to do the Getting Started tutorial on the site, but clojure.core.async isn't on the classpath when I run bin/repl
. Am I supposed to include it manually? The guide mentions nothing about it
The getting started tutorial uses the datomic client API (vs peer API) which uses core.async. Datomic free does not support client API so there isn't any point
Oh thanks so much I was gonna waste hours trying to figure that out lol
I know, I hesitate to say this but it feels obnoxious at this point
Older materials (e.g. Day of datomic) which start with the peer API will work with free
eugh, maybe I should just start with the starter though
Anyway thanks for that, spared me a lot of wasted effort
Free is so limited I wouldn't really use it unless I already knew datomic and had a particular app in mind which benefited from its licensing
Hi, I have a kind of broad modeling question. I’m trying to figure out the best way to support a dynamic data model. The simplest analogy would be something like what undergirds say, Google Forms or JIRA, where essentially, at runtime I can define a new field/attribute, that can then be used elsewhere. Datomic seems particularly suited to this, especially since apps that do this in a relational DB tend to use some sort of EAV anyway. This talk seems like a good approach (https://www.youtube.com/watch?v=sQCoTu5v1Mo), but was just wondering what other folks thought, and/or if there’s more recent ‘art’ on the subject
IIRC this talk talks about building self-describing databases with entity-level schemes. That's all well and good, but your problem is user-created attributes. Just like with a normal db, you probably don't want users creating their own schema--you need to reify their "attributes" as values : https://groups.google.com/d/msg/datomic/4clQqidRYJk/9hceY1hrno8J
I think we had a deeper discussion of this on this channel a long while ago but I can't find it
sweet thanks will check those out, yeah this isn’t really ‘true’ end users per se, but in my case more of an administrative function, where we can update some things in a more controlled manner but without a new deployment
Ok yeah, I think your approach has less ceremony than what was described in that video I posted. thanks
should database functions go in the :user
partition or an application-specific one?