Is it bad idea to rename DBI?

erthink / libmdbx

One of the fastest embeddable key-value ACID database without WAL. libmdbx surpasses the legendary LMDB in terms of reliability, features and performance.

https://erthink.github.io/libmdbx/

Other

1.16k stars 111 forks source link

Is it bad idea to rename DBI? #189

Closed AskAlexSharov closed 3 years ago

erthink commented 3 years ago

Rrenaming is not (historically) implemented, since these names are not visible to the end user and therefore renaming was never necessary yet.

On the other hand, it is not difficult to support it, if a reasonable use case will be shown.

AskAlexSharov commented 3 years ago

No real use-case, just our DBI names were created (historically) "somehow", and some of them was prefixes in LevelDB. Now we have DBI names like: "b", "B", "PLAIN-CST2", "clique-" But with lmdb/mdbx no reason to save characters on DBI names. It just would be nice to rename them to something meaningful without big db migrations.

AskAlexSharov commented 3 years ago

But it's not really important because we anyway plaining "non-backwards compatible release" to switch from LMDB to MDBX. And we can rename DBI's on APP side during that "non-backwards compatible release"