-
Notifications
You must be signed in to change notification settings - Fork 103
Issue 6321 - lib389 get_db_lib function may returns the wrong db type #6322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Added a test case and realized that there was also a problem in the off line case. |
|
Hum, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Commited new version with parametrized test (which is indeed simpler) |
…#6322) * Issue 6321 - lib389 get_db_lib function may returns the wrong db type get_db_lib returns the default db type instead of the configured one because of caught exceptions Fix the import issue if instance is online Fix the DSEldif parameter for the offline case Issue: #6321 Reviewed by: @tbordaz (Thanks!)
…#6322) * Issue 6321 - lib389 get_db_lib function may returns the wrong db type get_db_lib returns the default db type instead of the configured one because of caught exceptions Fix the import issue if instance is online Fix the DSEldif parameter for the offline case Issue: #6321 Reviewed by: @tbordaz (Thanks!)
…#6322) * Issue 6321 - lib389 get_db_lib function may returns the wrong db type get_db_lib returns the default db type instead of the configured one because of caught exceptions Fix the import issue if instance is online Fix the DSEldif parameter for the offline case Issue: #6321 Reviewed by: @tbordaz (Thanks!)
get_db_lib returns the default db type instead of the configured one because of caught exceptions
Fix the import issue if instance is online
Fix the DSEldif parameter for the offline case
Issue: #6321
Reviewed by: @tbordaz (Thanks!)