Skip to content
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

MigrateFromOTRS: specific message when DB connect is possible, but there are no tables #627

Closed
bschmalhofer opened this issue Nov 9, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@bschmalhofer
Copy link
Contributor

For testing I created a Postgres user and an empty schema. But I became confused because the message said that the connect was not possible. The real reason why the check failed was that there were no tables.

@bschmalhofer bschmalhofer added the enhancement New feature or request label Nov 9, 2020
@bschmalhofer bschmalhofer added this to the OTOBO 10.0.6 milestone Nov 9, 2020
@bschmalhofer bschmalhofer self-assigned this Nov 9, 2020
bschmalhofer added a commit that referenced this issue Nov 9, 2020
add explicit check whether the database connect works
bschmalhofer added a commit that referenced this issue Nov 9, 2020
Issue #627: enhance the reporting from SanityCheck
@bschmalhofer
Copy link
Contributor Author

Enhanced the error message when the sanity check fails.

@bschmalhofer
Copy link
Contributor Author

The messages emitted when the hostname is incorrect, or when there are no tables, is now more sensibel. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant