Add bdb deprecation FAQ #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vashirov
reviewed
Oct 18, 2023
tbordaz
reviewed
Oct 19, 2023
docs/389ds/FAQ/bdb-deprecation.md
Outdated
| Mixing implementaions limitations are: | ||
|
|
||
| - The db_lib parameter is stored in the nsslapd-backend-implement attribute of cn=config entry, so it is global to the instance. | ||
| - backup / restore formats are tied to the db implementation so you cannot use a backup to restore an instance with a different implementation. (ldif export/import and initializing through the replication have not this limitation) |
There was a problem hiding this comment.
Should we mention impact on guardian and DB_VERSION ?
droideck
reviewed
Oct 19, 2023
progier389
force-pushed
the
nobdbfaq
branch
3 times, most recently
from
a735a20
to
b7e4993
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add bdb deprecation FAQ
Reviewed by: @vashirov, @tbordaz, @droideck Thanks !