GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Consider to support bindings for MDBX · Issue #281 · lmdbjava/lmdbjava

Consider to support bindings for MDBX #281

New issue
Copy link
New issue
Copy link
Open
Feature
Open
Consider to support bindings for MDBX#281
Feature
Copy link
Labels
questionQueries on usage of the library, architectural patterns and alikeQueries on usage of the library, architectural patterns and alike

Description

@cdprete
cdprete
opened on Nov 20, 2025
Issue body actions

Hello.

MDXB is a fork of LMDB which provides some very good additional goodies.
Read https://github.com/erthink/libmdbx for more details.

It would be great if LMDB Java could be expanded to support that fork as well.
Alternatively, an MDBX Java library could potentially be initiated to support it in parallel.

There is indeed a binding library already available, but it's not as maintained as this one. :)

Reacted by Andrej Fink
Reacted by Andrej Fink

Activity

  1. at055612
    added
    questionQueries on usage of the library, architectural patterns and alikeQueries on usage of the library, architectural patterns and alike
    on Nov 21, 2025
  2. at055612 commented on Nov 21, 2025

    @at055612
    at055612
    on Nov 21, 2025
    Collaborator
    More actions

    My view is that such a thing should be a separate project. While mdbx my be similar to lmdb now, it is a fork so may well diverge. It would add unnecessary complexity to LJ for people that are only interested in lmdb as a back-end.

    Reacted by Mark Wardle
  3. cdprete commented on Nov 21, 2025

    @cdprete
    cdprete
    on Nov 21, 2025
    ContributorAuthor
    More actions

    My view is that such a thing should be a separate project. While mdbx my be similar to lmdb now, it is a fork so may well diverge. It would add unnecessary complexity to LJ for people that are only interested in lmdb as a back-end.

    Yep, indeed I agree it should go in a separate project/repo.
    The idea here was more about evaluating if the current bindings, as well as the additions (e.g.: key ranges), could be easily reused.

  4. at055612
    added the
    Feature
    issue type on Apr 24, 2026
  5. at055612 commented on Jun 8, 2026

    @at055612
    at055612
    on Jun 8, 2026
    Collaborator
    More actions

    It looks like libmdbx is becoming mithrildb and going closed source.

    https://github.com/Mithril-mine/libmdbx#mithrildb-and-future

    @cdprete are you happy to close this issue?

  6. cdprete commented on Jun 8, 2026

    @cdprete
    cdprete
    on Jun 8, 2026
    ContributorAuthor
    More actions

    It's still maintaned, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionQueries on usage of the library, architectural patterns and alikeQueries on usage of the library, architectural patterns and alike

    Type

    Feature

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.