Fork me on GitHub
#datomic
<
2017-10-10
>
akiroz04:10:29

I guess I'm doing something stupid but I've been stuck trying to transact a schema for quite a while now. Getting java.lang.IllegalArgumentException: :db.error/not-an-entity Unable to resolve entity: :db/indent when I called (datomic.api/transact conn [{:db/indent :foo/bar :db/valueType :db.type/string :db/cardinality :db.cardinality/one}])... I'm on version 0.9.5561.59 any ideas?

akiroz06:10:52

Ok, I found the problem..... misspelt ident -> indent, my guess was right. (facepalm)

djjolicoeur17:10:29

adding an index to an attribute happens in a background process on the transactor, correct? does it degrade service on running peers at all, other than using resources?

djjolicoeur18:10:37

I just want to make sure I understand the process

djjolicoeur18:10:51

an existing attribute, that is

djjolicoeur18:10:06

and is there a way to monitor progress?

djjolicoeur19:10:43

other than monitoring sync-schema, which I guess I could easily script something out around

eoliphant20:10:00

Hi, I have a quick collections question. I’m doing some stuff with datomic and of course you’re kind of on the hook for your own paging. I’m trying to implement cursor based paging such that I can give a key value then return that item, plus N items ‘in front’ or ‘behind of it’ So for the following

({:id "A" :val..} {:id "B" :val..} {:id "C" :val..}{:id "D" :val..} {:id "E" :val..})
If I have say “C” and ‘2 behind’, I get A,B,C. Or “C” and ‘one after’ would give me C and D. and of course, it’d be nice if it was reasonably performant. Any suggestions?