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

Column name is parsed as broken MultipartIdentifier if inline PK defined

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
sql
Domain
compilers

Research direction

Start by running the minimal T-SQL reproduction against ScriptDom 170.28.0 and inspecting the resulting AST for the IdObject column. Trace how the inline PRIMARY KEY is parsed, then verify that the column name is represented normally with valid indexes and ScriptTokenStream data when the repro is parsed.

Written by the indexing model from the issue text.

Description

ScriptDom version: 170.28.0

If column is marked as PRIMARY KEY inline then it begins to be parsed as MultipartIdentifier with a single identifier and all the other properties missing (-1 for indexes, null for ScriptTokenStream)

Minimal repro:

DECLARE @Results TABLE (IdObject INT NOT NULL PRIMARY KEY);

Image

if I remove PRIMARY KEY the column name is not parsed as MultipartIdentifier anymore and the error goes away.

Dominant language
GAP
Stars
277
Forks
43
Avg merge
6d 17h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

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/SqlScriptDOM

All issues in microsoft/SqlScriptDOM

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.