Fork me on GitHub
#datomic
<
2018-10-22
>
mkvlr10:10:41

there hasn’t been any progress on https://groups.google.com/forum/#!topic/datomic/kOBvvc228VM has there? We’d also like to vote for getting more info on the exception. We’d like to know which attribute(s) cause the db.error/unique-conflict without having to parse the string…

joshkh19:10:41

any ideas? java10 on a fresh ec2 instance: Caused by: java.lang.IllegalArgumentException: Can't define method not in interfaces: recent_db, compiling:(datomic/client/impl/shared.clj:304:1)

eoliphant20:10:15

I think I've seen some other weirdness mentioned with j10. We're moving all of our stuff to cloud, but still using 8 for on-prem

eoliphant20:10:34

ah wait is that client code ?

joshkh20:10:24

yup! client code. my project compiles fine on my local machine (with the same jvm), but now i have a hunch that i've juggled quite a few deps via lein install and maybe can't reproduce their order on a remote machine. yikes.

joshkh20:10:06

when in doubt, uberjar? :man-shrugging:

donaldball21:10:52

It’s my observation that d/release on a memory connection actually deletes the underlying database. This is reasonable behavior, but the documentation doesn’t suggest it’s intended. Can anyone on the datomic product team clarify by any chance?