Fork me on GitHub
#datomic
<
2021-06-07
>
tatut11:06:19

I know bigdec scale should be consistent, but I find this is weird: I have a tx that has a scale only change

[109951162801971 360 6.880M true]
 [109951162801971 360 6.88M false]
but I can’t reproduce it… If I try to do that again, I get “two conflicting datoms” error from transact

tatut11:06:26

I only noticed because our custom backup/restore failed to restore because of the transaction exception. The version of datomic compute group hasn’t changed from when that first tx was created

tatut04:06:17

The same is mentioned in datomic cloud, but I don’t see any more details on it… and why does it say “two conflicting datoms” when I try to recreate this situation