microsoft / microsoft/go-sqlcmd
Output data is not easy to parse
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
In CLI mode, the returned data sometimes needs to be used in scripts or automation.
It therefore would be nice if the returned data would be easily parse-able. It would be nice if an output format could be selected, like CSV, JSON, XML, etc.
I'm aware that I could define a separator in horizontal output format. But unfortunately the output values won't be returned with quotes if the values themselves contain the separator character, making the parsing a big pain.
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 tracing CLI mode's output path and the horizontal output/separator handling described in the issue. Compare the parsing requirements for CSV, JSON, and XML, including values containing separators, and define how a format can be selected. Done means selected formats produce reliably parseable output for scripting and automation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- cli, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100