Clojurians Log v2

Hey @jeremys. What is the exception being thrown?

I don't know what to think of it, it's like the layout of the data in the underlying array map influences the outcome. At least that all I an think of...

yes it does, interesting. my guess is that the schema is updated in an order where the prior schema key-value pairs are missing and that is how it trips (although i am not sure why it yields a long yet). can you open a bug report? i guess we will have to ensure a specific ordering for schema maps that are transacted

I can, I'll add the example to the issue.

I created an https://github.com/replikativ/datahike/issues/754. Thanks

@jeremys are you blocked on this? also, what direction are you interested in?

I am not blocked, I discovered this while making a tiny helper to declare schemas. I have fixed my helper so that it ensures the :db/ident is the first thing that goes into the map declaring the tuple schema. Since then I can move on to playing with datahike, no problem. Still someone else might randomly come up on this and be as puzzled as I was. Better to report it then.

for sure, this should not happen