Konrad Kühne

Could you check if that works with the latest rebase as well?

We have to check this again with the new backends.

So, your are updating multiple schema-attributes in one transaction?

If you are running this in a repl, what does `*e` print? The `:invalid-updates` in the `ExceptionInfo` data might give some information.

Thanks @jjtolton , I'll get to it in the next days.

I'll add it to the 0.2.2 release and mention you in the change log if that is alright.

Thanks for the info @theronic. I'm working on a remote transactor now with a new connector in Datahike itself. This will include pool connections.

I found this issue as well and fixed it in my development branch. Should be available in the next release.

In addition I'll create a document about what datomic features are supported and what is different.

Thanks for reporting that @zoren. What additional features do you use? Like `keep-history?`, `attribute-refs?`and what kind of backend?