This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-02
Channels
- # beginners (61)
- # boot (84)
- # cider (43)
- # cljsrn (2)
- # clojure (99)
- # clojure-android (3)
- # clojure-austin (2)
- # clojure-italy (5)
- # clojure-russia (43)
- # clojure-spec (93)
- # clojure-uk (41)
- # clojurescript (94)
- # clojutre (1)
- # cloverage (8)
- # core-async (31)
- # cursive (3)
- # datomic (14)
- # defnpodcast (1)
- # editors-rus (7)
- # events (1)
- # hoplon (15)
- # leiningen (3)
- # luminus (6)
- # om (142)
- # onyx (86)
- # other-languages (4)
- # pedestal (1)
- # planck (1)
- # portland-or (5)
- # re-frame (96)
- # reagent (16)
- # ring-swagger (17)
- # rum (73)
- # specter (25)
- # untangled (14)
- # yada (142)
@marshall I can prepare a repo and mail you when I’m finished.
@teng Learndatalogtoday has a DB that was generated prior to the fix I believe. That is why it still exhibits this error. Any DB created prior to Datomic 0.9.5206 will have this issue.
@teng I bumped the datomic version and redeployed learndatalogtoday. Could you check if ths solves the issue?
@jonas Now it works. Thanks!
When using Datomic from Java without ever initializing Clojure myself, how can I avoid "No reader function for tag db/id"
errors when reading Datomic schema from EDN via datomic.Util.read(ednString)
?
I've tried clojure.var("clojure.core/require").invoke("datomic.api")
based on my google searches, but it had no effect on resolving this error.
<stab-in-the-dark>
Curious if calling (#'clojure.core/load-data-readers)
after your require
might help.
</stab-in-the-dark>
anyone put much thought into modeling translations inside datomic? For instance if I have simple entity like
:content/name
:content/description
:content/type
but I want name and description to be able to be translated into multiple languages. Curious what others have done? I have done this in RDBMS and that would translate ok, just wondering if there is better way.I think the obvious may be to just do [property]-[isocode]
so like have :content/name-es
and :content/name-cn
etc…?
My other thought is to create an entity like this:
:translation/iso
:translation/attribute
:translation/text
Then in my content entity I’d have an attribute of :content/translations
An aside, I’d be very interested in book/blog series/etc… on datomic data modeling best practices!