Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2023-05-19

Channels

#datomic
<
2023-05-19
>
enn14:05:41

I see that the Cloud docs state a limit of 1024 digit precision for BigDecimals, while the on-prem docs do not. Does that mean on-prem supports true arbitrary precision for BigDecimals?

souenzzo16:05:09

I think that the answer is the same as in strings: strings in cloud are explicitly limited in 4096 chars long in cloud, in on-prem, there is no limitation inside datomic code, but it may break in some other part of your system (JVM, dynamodb, SQL command size, etc..)

enn15:05:55

I’d also like to better understand the behavior alluded to here when scales don’t match: > • Consistent results in query depend on the scale matching for all BigDecimal comparisons. You are strongly encouraged to use a consistent scale per attribute. If I will never query by this value, do I need to worry about mismatched scales? (I’m considering using a BigDecimal attribute to represent a position in an ordering, so I only care about the relative magnitude of the values.)

Henrique Prange20:05:14

I am experiencing a discrepancy between dev-local and client-cloud when querying Datomic passing :timeout nil. In dev-local, the query works as expected, but in Datomic Cloud, it fails with a Datomic Client Exception. I’m using dev-local 1.0.243 and client-cloud 1.0.123.