Fork me on GitHub
#datomic
<
2018-03-06
>
alex.gherega10:03:14

hi guys, I'm getting "Cannot write 210 as tag null when transacting a 210N" on datomic for cloud. can anyone explain this?

marshall13:03:05

@alex.gherega Can you provide the full error / stack trace ?

marshall13:03:59

looking into it

dominicm16:03:11

ah, they've moved to /on-prem/, looks like duck duck go hasn't picked that up yet.

marshall16:03:30

ah, yeah i was going to ask where you found that link

dominicm16:03:30

/index.html

dominicm16:03:42

@marshall first my history, then duck duck go 😛

marshall16:03:45

search engines are tough - not much we can do about that 🙂

marshall16:03:59

i can update all our own internal links (and have been trying to)

dominicm16:03:29

Well, HTTP 301 is the proper approach, no? Whether or not S3 let you do that, I don't know.

dominicm16:03:07

https://docs.datomic.com/on-prem/javadoc/index.html The link to "entity id" does nothing, just while I'm at it 😛

marshall16:03:09

hm. i’ll have to have a look

dominicm16:03:29

(it's also to the wrong place, probably relevant)

marshall16:03:00

@dominicm i’ve fixed those links. i will look into the path without index.html

sparkofreason17:03:21

Suppose I'm storing timestamped entities, and want to retrieve the N with the most recent timestamps. How would you do that using Datomic Cloud?

souenzzo17:03:18

On peer, you can query by all entities, sort-by inst and take n. but on cloud/client, I'm curious to know once query all entities can be potentially huge. For client, sort on query is a missing feature.

marshall18:03:49

I would use a nested query

marshall18:03:00

depending on whether your timestamps or the entities are the more restrictive, i’d either find the N most recent or find all relevant entities in the inner query

sparkofreason18:03:22

That's pretty slick. Thanks.

souenzzo17:03:18

On peer, you can query by all entities, sort-by inst and take n. but on cloud/client, I'm curious to know once query all entities can be potentially huge. For client, sort on query is a missing feature.

cjsauer20:03:27

Fun aside: just bragged about our company's use of Datomic on a client call, mainly surrounding its data history capabilities and analytic flexibility, and they were blown away metal

erichmond23:03:19

My company was primarily acquired because of the last product we built, which was in clj/cljs/datomic, and their CEO was legit blown away by the stack, datomic in particular