Fail gracefully when connecting to other database #3026
Merged
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.
Fixes #2627
I'm currently working at Forest Admin.
We're a French company building a SaaS that generates admin panels.
During onboarding, we connect to our customer's databases to introspect the structure.
However, customers don't always know which database vendor they are using, and click on the wrong one during onboarding.
This causes pg-protocol to throw an unhandled exception, and our backend workers to go down.
I tried to follow the coding style and test this.
Don't hesitate to come back to me if anything is not at it should be!
Note that I never managed to run all the tests locally... so I'm likely to break others.
I'm creating the PR so that the CI runs, and that I can check if everything is OK