squash db migrations#280
Merged
Merged
Conversation
zcroft27
approved these changes
Apr 22, 2025
Contributor
zcroft27
left a comment
zcroft27
left a comment
There was a problem hiding this comment.
Great idea--ship it 🚢 😭 😿😿😿😿
This file contains hidden or 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
2 participants
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.
this replaces our messy migration scripts with a single script for creating all of our tables, based on their current Supabase definitions (this accounts for any changes made directly in Supabase without a migration script). this should make it more seamless for someone to recreate our DB, and it also makes it easier to see what's going on in our schema at a glance.
i also added an insert script to populate the DB with the set of emissions_factors we've been working with