Database DDL & Migration Support for plugins
- Dominant language
- Go
- Stars
- 15.7k
- Forks
- 1.4k
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 7
Description
## Is your feature request related to a problem? Please describe
Apache Answer should support a way for plugin devs to have DDL and migration specific to their plugins / code.
There are plenty of use cases for this.
Most basic use cases is their tables would act as meta for their plugins.
## Describe the solution you'd like
Apache Answer should support a way for plugin devs to have DDL and migration specific to their plugins / code.
## Describe alternatives you've considered
Alternative is plugin having its own database. This idea sucks when you have use cases of joins between answer db to plugin db.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the plugin lifecycle and the existing database DDL and migration mechanism. Done means plugin developers can define and run plugin-specific schema changes while keeping those tables in the Apache Answer database for joins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100