Niklas Schlimm

Hi mate, if you have some field on your customer object saying if „John“ is a customer or is not a customer (e.g. a boolean field), then you would no...

The best way to understand the concept is to realize that there is no deletion in bitemporal data. There is just a NEW OBECT STATUS created saying that, from a...

Hi Stefan, thanks for the question and reference. By default BarbelHisto is document-oriented, therefore there should never be a candidate for coalescing. There will never be overlapping or adjecant „tuples“...

I will take a look at this one soon ...

Looked deeper into this issue. CQEngine uses Kryo to serialize/deserialize objects to SQLLite. Kryo isn't Java 17 compatible right now. There is already an issue there complaining about this fact....

The master branch already uses `Bytebuddy ` as standard proxying library. That should be enough to run barbelhisto core in JDK 17 envirnoments as long no `DiskPersistence ` is involved...

Version 2.2.0 using Bytebuddy should work in JDK 17 as long no DiskPersistence / SQLLite / Kryo Serialization is required. I have to wait for my dependencies to follow up...

Hi Hristo! Thanks for your attention :-) BarbelHisto is meant as a lightweight, easy to understand and use, scalable solution for NoSql Databases. It‘s not meant to compete with Hinernate...

Hi Hristo ! I will put that NoSql disclaimer upfront in the docs ... I agree ... the complexity that comes with OR-mapping is one reason for me to use...

BTW: BarbelHisto provides disk persistence and SQL-like indexed quries on the collection ... this pair is blazing fast compared to the assembling required in OR solutions ... on the other...