hasura / hasura/graphql-engine
migrating individuals objects
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Is your proposal related to a problem?
Always when my team forgets to enable hasura console for making migrations when they're creating new tables or fields, we have to create in another environment manually the tables.
### Describe the solution you'd like
I think it would nice in some way that we can migrate selected elements instead the full schema just because we built a table
### Describe alternatives you've considered
I have no idea in this moment
Contributor guide
Research direction
The issue names no files, tests, or entry points. First clarify how selected tables or fields should be migrated instead of the full schema, then identify the existing migration workflow and define the expected behavior and completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100