389-ds-base

#49483 investigate if backend get|set entrypoint is needed
Closed: wontfix by spichugi. Opened by lkrispen.

Closed: wontfix
Reopen Issue

We have the functions 

 slapi_be_setentrypoint
 slapi_be_getentrypoint

They set and return functions in the be_database plugin struct. But they are no tcalled with this usage, the only call is slapi_be_setentrypoint from the chainig backend, with a pblock parm, which triggers a very special, different handling to set the cb plugin in th ecb backend. jus because the Struct backend is not avialbel in the cb plugin.

I think it would be better to provide a specific function:

 slapi_be_set_dbplugin( backend, plugin)

and get rid of the get/set entrypoints

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4 backlog

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/2542

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.