Nikita Prokopov
Nikita Prokopov
Ok, thank you. I pushed 1.0.3 for now that disables transient indices. Later I’ll take a more detailed look into it. Please leave this issue open
@darkleaf issue probably was in transient indices + restarting transaction after tempid resolve (db/retry-with-tempid). Note: I disabled transient indices in latest version.
@filipesilva They are not implemented in CLJS, no need to worry. JVM version is now fine too, I turned them off, will fix later
I’m sorry, I don’t know. Maybe it’s worth building one?
Total compare function is great, but re-implementing it for every Clojure and Java type might be too much? On the other hand, maybe there’s not much work, in that case...
Another solution might come from the user, who might decide not to store vectors of arbitrary types?
> It just works because we haven't a better solution, doesn't it? Yes. Maybe identityHashCode would be better, if it’s based on object pointers addresses (needs checking)?
Replacing schema is trivial to do in user code. What I don't want to do is to provide schema altering fn that will do that and ignore all the issues...
I think schema migration should work one of three possible ways: 1. Always accept changes if they are safe (one to many, unique to non-unique) - adjust internals if needed...
Seems fine, but `merge` should be something like `merge-with merge` and patch applied over schema. The validation will be very tricky, which is the main reason I left it unimplemented....