I'm finding pull syntax dramatically slower (4x) than binding all the return values i want with where clauses. Any ideas why that might happen?

Anyone experienced this error? No implementation of method: :value-size of protocol: #'datomic.cloud.tx-limits/ValueSize found for class: java.lang.Integer It only happens in cloud during a specific transaction. I cannot reproduce this localy 😕

@rhansen that's a known issue with transacting a java Integer. Fix pending.

Ahh, ok. Should be an easy fix 😊

I realize now that the previous statement can sound a bit rude. I ment it should be easy to work around on my end, not that it should be an easy bug for you to fix on your end 😅

Hello all, Hopefully simple question about Datomic Cloud. If I’m understanding the Datomic Cloud documentation on pricing correctly, you can run Datomic Solo Topology for $1/day, but if you want to scale (for either performance/capacity or HA) the next step would be to switch to Datomic Production Topology which would start at about $15/day (two i3.large instances). Is that reading correct?

So I want to pass a pattern to a pull using :in $ pattern and the pattern has a list of attributes like [:input/name :input/value] except only the first attribute is coming back. If i hardcode the pattern with pull ?e [:input/name :input/value] everything works as expected. I just upgraded to version 0.9.5703 after reading @marshall's comments in this thread: https://clojurians-log.clojureverse.org/datomic/2018-03-15

ultimately my goal is to pull using an om-next ast sent from the client. not sure if there are workarounds here but i'm surprised that passing the pattern as an argument works differently than hardcoding the pattern.

@austinbirch yes. But if you use reserved instances that price goes down by a noticable amount.