microsoft / microsoft/go-sqlcmd
Allow user to restore a database into container once container already running
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
It would be good to have a way for the user to use sqlcmd to restore another database into the container post create. while the --using <filename.bak> is functional on the create, if I wanted to restore something else into the container I have to futz with things to make it work and if you aren't a container person that might be difficult.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sqlcmd create flow and its existing --using <filename.bak> handling. Trace how database restore is performed during container creation and determine the entry point for restoring another database after the container is running. Done means a user can invoke sqlcmd to restore a database post-create without manually adjusting the container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100