For UPDATE statement, visitor visits SetClauses after WhereClause
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start with the TSqlFragmentVisitor entry point and reproduce the UPDATE traversal using overrides for AssignmentSetClause and WhereClause. Trace the UPDATE statement's visitor order and add coverage for the expected sequence; done means AssignmentSetClause is visited before WhereClause.
Written by the indexing model from the issue text.
Description
.NET Framework (Windows-only) or .NET Core: .NET 8
Environment (local platform and source/target platforms): net8.0-windows x64
Steps to Reproduce:
Create a visitor inheriting from TSqlFragmentVisitor
Override ExplicitVisit(AssignmentSetClause node)
Override ExplicitVisit(WhereClause node)
Item 2. (AssignmentSetClause) gets invoked "after" Item 3. (WhereClause)
Shouldn't this be reversed?
- Dominant language
- GAP
- Stars
- 277
- Forks
- 43
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 3
Contributor guide
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.
More from microsoft/SqlScriptDOM
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/SqlScriptDOM#228 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/SqlScriptDOM#183 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
microsoft/SqlScriptDOM#226 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/SqlScriptDOM#225 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
microsoft/SqlScriptDOM#224 ·
All issues in microsoft/SqlScriptDOM
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
splunk/token-meter#56 ·
-
Doc: Oppdater README Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100