MPP-3931: Enable pgcrypto #5089
Merged
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
groovecoder
requested changes
Oct 10, 2024
groovecoder
approved these changes
Oct 10, 2024
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.
Enable the pgcrypto extension for PostgreSQL, which allows using server-side cryptographic hashes. This is considered "trusted", so the
CREATEprivilege is enough to enable it.I also adjusted the database configuration so that it can get
DATABASE_URLfrom the.envfile as well as the environment. This allowed me to confirm the migration runs on both SQLite and PostgreSQL.How to test
CircleCI tests should be sufficient to test the migration.