Fork me on GitHub
#datomic
<
2016-09-02
>
tengstrand05:09:06

@marshall I can prepare a repo and mail you when I’m finished.

jaret13:09:07

@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.

jonas17:09:23

@teng I bumped the datomic version and redeployed learndatalogtoday. Could you check if ths solves the issue?

tengstrand17:09:30

@jonas Now it works. Thanks!

sdegutis20:09:11

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)?

sdegutis20:09:24

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.

rwtnorton21:09:19

<stab-in-the-dark> Curious if calling (#'clojure.core/load-data-readers) after your require might help. </stab-in-the-dark>

sdegutis21:09:21

Never mind, it works with readAll which takes a stream. That works for now.

adammiller23:09:23

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.

adammiller23:09:27

I think the obvious may be to just do [property]-[isocode] so like have :content/name-es and :content/name-cn etc…?

adammiller23:09:56

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

adammiller23:09:11

An aside, I’d be very interested in book/blog series/etc… on datomic data modeling best practices!