#47567 dbscan option to print in LDIF format
Closed: wontfix 2 years ago by mreynolds. Opened 8 years ago by rmeggins.

Would be nice to be able to make a database dump in LDIF format from dbscan.

For the main entry database, it would probably be something like this:
iterate entryrdn.db in parent child order - for each dn
grab the entry from id2entry.db
print the dn + entry data in standard LDIF format
+ for replication, need to have a way to strip replication metadata

For the changelogdb, it's already close to the changelog ldif format, so it shouldn't take too much


Metadata Update from @rmeggins:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.4 backlog

5 years ago

Do we want this to be the default behaviour of dbscan when we do "dbsacn -f id2entry.db" for example? Or only when we pass a flag or something to dbscan?

Metadata Update from @ilias95:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None

4 years ago

Do we want this to be the default behaviour of dbscan when we do "dbsacn -f id2entry.db" for example? Or only when we pass a flag or something to dbscan?

It should be a new option that takes a directory as the parameter value:

dbscan -p /var/lib/dirsrv/slapd-instance/db/userroot

Metadata Update from @mreynolds:
- Issue tagged with: RFE

4 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/904

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata