GROUP-105 Updated Flyway URL to Correctly Identify sslRootCert #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Changes
It turns out that Flyway doesn't recognize the use of ampersands (&) to delimit properties in a JDBC URL. Instead, it recognizes only semicolons (;) as the delimiter. Many examples online use ampersands to delimit properties in a JDBC string, but there are docs that specify the use of semicolons.
Sources on using semicolons:
MS SQL Server
Java Docs
PostgreSQL
The PostgreSQL docs show an example using ampersands, so it's kind of weird why only semicolons work in the Flyway URL. Maybe a JDBC driver restriction?