microsoft / microsoft/go-sqlcmd
Go + tab is not understood.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
I have the attached file slask.sql. When I run it this happens:
The issue is that the second go is followed by two tab characters and go-sqlcmd does not recognise the situation. It works in old SQLCMD and in SSMS.
Note: The actual situation I ran into this is the creation script for the Northwind database.
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 reproducing the behavior with the attached slask.sql file, focusing on the second GO followed by two tab characters. Compare go-sqlcmd's handling with SQLCMD or SSMS, and consider the issue done when that input is recognized and executes as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- cli, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100