[COR-618] Add updated_at timestamp for new extensions
#245
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
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
EvanHStanton
approved these changes
Apr 13, 2023
sjmiller609
added a commit
that referenced
this pull request
Dec 5, 2023
* wip * Remove changes in toggle_extensions * Fix tests * automatically enabling shared_preload_libraries * Move to new file trunk.rs * wip: fetch from trunk * Undo changes from revert * fix crd * Fix build * Use list from trunk * fmt
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.
When a new extension is created, add
updated_attimestamp (same ascreated_at) to the new extension record. This fixes an issue when listing extensions at https://registry.pgtrunk.io/extensions/all.Related to: