Cosimo Damiano Prete

> I think the only way to compact space is using mdb_copy (`org.lmdbjava.Env#copy` with `org.lmdbjava.CopyFlags#MDB_CP_COMPACT` in lmdbjava) which copies the whole db into a new one and compacting at the...

Hi @at055612. The weird thing is that the exception happens from time to time even when the disk is not full at all (e.g.: only 28% is used). Nevertheless, I'll...

I can confirm as well that the `KeyRange`s are somehow broken. In my case I'm using `KeyRange#closed`.

> The changes in v0.9.0 have broken CursorIterable for some KeyRange types and keys. I noticed the problem when using `KeyRange.atLeastBackward(`. The cursor was starting on the wrong key. >...

> Hi No, it was not working, see my comment > […](#) > > Supplying MDB_INTEGERKEY also does not work, not clear to me why On Mon, 5 Feb 2024...

> Hi @cdprete I took your pull request and added extra flag so the open looks like > > `Dbi db = _env.openDbi(hexId, MDB_CREATE, MDB_UNSIGNEDKEY);` > > I guess that's...

Hi @ivenhov. May I ask you to test it again? I've realized in some spots I missed to skip the additional flag (fixed now). :) Also, have a read at...

Hi. I agree (so, to add a MDB_SIGNEDKEY flag instead to still support both), but it would then yet be another breaking change when compared against v0.9.0. Of course, it's...

> I came across this same issue upgrading from 0.8.3 where our LMDB tables used `ByteBuffer.putLong( _rowId )` for the keys. When we tried to retrieve `_rowId=127` (`Byte.MAX_VALUE`), the new...

> This would seem to be an issue with running lmdb 0.8.3 on centos 7. 0.8.3 runs fine on other OSs, e.g. arch, alpine. Rolling back to 0.8.2 fixes the...