microsoft / microsoft/go-sqlcmd
Add a "not yet implemented" error for all back-compat switches so user gets an actionable error message
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
If there are any switches left from the old ODBC sqlcmd that are not yet implemented in the new go-sqlcmd, please put in a stub implementation for go-sqlcmd now, which gives an actionable error message.
We are seeing some cases where go-sqlcmd is being drop in replaced with the old ODBC sqlcmd and the swithch synatac isn't identical (-N right now is an example, -N in go-sqlcmd needs a parameters, e.g. -N true, whereas in ODBC sqlcmd, it is just "-N")
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 by comparing the old ODBC sqlcmd switches with the go-sqlcmd command-line parsing and identify switches that are not implemented. Check how the existing -N handling reports invalid usage, then add stub behavior for each missing switch with an actionable error message; done means unsupported back-compat switches no longer fall through to an ambiguous failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100