Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add a "not yet implemented" error for all back-compat switches so user gets an actionable error message

Open
#496 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, sql
Domain
cli

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.

Description

enhancement sqlcmd switch

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")

Dominant language
Go
Stars
595
Forks
91
Avg merge
9h 35m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/go-sqlcmd

All issues in microsoft/go-sqlcmd

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.