Hi, I am trying write a parametrized query that returns n random elements. The following query works:

(d/q '[:find [(rand 10 ?m) ...]
                      :in $ 
                      :where [?m :cliente/name]]
                    db )

(d/q '[:find [(rand ?n ?m) ...]
                      :in $ ?n
                      :where [?m :cliente/name]]
                    db 10)

hi guys can we use isComponent on enum type ?

@lboliveira: my guess is that Datalog is not dynamic about this

you'll probably want to build the query data structure programatically as a workaround

@nxqd: I think so. I am using without any issues.

@lboliveira: thanks for letting me know, I use datomic-schema, it does seem to have problem with component. I might just use plain datomic schema in the future then

@nxqd: i am using datomic-schema too:

(s/schema foo
             (s/fields
               [type :enum [:type-a :type-b] :component]
               [ref1 :ref]
               [ref2 :ref]))])

and this works

what is happening?

@lboliveira: cool, thanks. my mistake

I put :component between :enum and its values xD

😃

@val_waeselynck: =(

can someone shed some light on how to interpret the MemoryIndexMB metric in Datomic?

ours bounces up and down like that everyday

not sure if it’s something to worry about

@kschrader: MemoryIndexMB is the size of the ‘memory index’ - that is the part of the index with novelty that has not yet been incorporated into the disk index.

ahhh

ok, that’s not how I read it

but it makes sense now

@kschrader: I would expect that pattern. As the memory index size approaches the MemoryIndexThreshold, a background indexing job will incorporate that data into the disk index

so the drops you see are likely right after the completion of an index job

@kschrader: docs on the memory index are here: http://docs.datomic.com/caching.html#memory-index

got it

perhaps the metrics table on the monitoring page could link out to the longer definitions in the docs

it’s not always clear how to interpret all of them

@kschrader: noted, I can take a look at adding more links to the relevant sections that explain what the metrics correspond to.