nimdbx icon indicating copy to clipboard operation
nimdbx copied to clipboard

Fast persistent key-value store for Nim, based on libmdbx

Results 10 nimdbx issues
Sort by recently updated
recently updated
newest added

``` ~/nimdbx/nimdbx/Cursor.nim(106, 6) Error: 'pastMinKey' can have side effects > ~/nimdbx/nimdbx/Cursor.nim(106, 43) Hint: 'pastMinKey' calls `.sideEffect` 'compareKey' >> ~/nimdbx/nimdbx/Cursor.nim(92, 6) Hint: 'compareKey' called by 'pastMinKey' ```

I get `Error Type` when hovering over `mdbx_` symbols in VS Code. Is this expected? - nim 1.5.1

I'm getting this error: ``` MDBX_BUSY: Another write transaction is running, or environment is already used while opening with MDBX_EXCLUSIVE flag ``` Is there a workaround for this?

I found your thread: https://forum.nim-lang.org/t/6301#38854 I'm trying to use `getCollectionOrNil` but I can't prove to the compiler that the collection is non-nil by using `raise` within a `if col ==...

``` Compiling C:\nimdbx\tests\test1_Data (from package nimdbx) using c backend # Including library C:\nimdbx\libmdbx-dist\libmdbx.a # Importing C:\nimdbx\libmdbx-dist\mdbx.h # Saved to C:/Users/asus/nimcache/nimterop/toastCache/nimterop_2496732934.nim C:\nimdbx\nimdbx\private\libmdbx.nim(56, 8) template/generic instantiation of `cImport` from here C:\Users\asus\.nimble\pkgs\nimterop-0.6.13\nimterop\cimport.nim(704, 10)...

```nim import nimdbx let CollectionName = "stuff" var db = openDatabase(".") var coll = db.createCollection(CollectionName) ``` error as follows: ```shell # Running make # Path: C:\Users\asus\.nimble\pkgs\nimdbx-0.4.1\libmdbx-dist stack trace: (most recent...

There seems to be a problem with libmdbx building on Windows in a Github Action. I filed https://github.com/erthink/libmdbx/issues/138 . Until then I'll disable Windows in CI.

The key/value API is awkward because keys and values can be anything. Data and DataOut help, but aren't very safe. It would be nice to have generic KEY and VALUE...

MDBX_cursor supports writing to the collection, if it's in a write-transaction. Should support this (with a `WriteCursor` subclass.)