Skip to content

Use PostgreSQL lexical rules in the standard Duplication Browser - #30

Open
deem0n wants to merge 2 commits into
fix/14-sql-source-browserfrom
fix/17-sql-duplication
Open

deem0n wants to merge 2 commits into
fix/14-sql-source-browserfrom
fix/17-sql-duplication

Conversation

@deem0n

@deem0n deem0n commented Sep 20, 2026

Copy link
Copy Markdown
Owner

The default C-like cleaner treats SQL comments and quoted text incorrectly. Add an explicit PostgreSQL cleaner to the existing settings and an openOn: preset using the standard browser.

Handles -- comments, nested block comments, quoted identifiers, doubled quotes, E-string escapes, dollar quoting and line mapping. Literal whitespace stays significant; malformed lexical input fails explicitly. Assumes standard_conforming_strings=on and compares dollar bodies verbatim. No semantic clone-equivalence claim.

Validation: 6 tests passed in an isolated Moose 13 image, including nested comments/token boundaries, literal-difference negative case, escaped/multiline literals, malformed input, actual FamixRepDetector fragments and codeText with SQL owner anchors, and the real standard browser cleaner selection.

Tracks #17. Stacked on #27/#25 for optional UI packaging and source-anchor prerequisites. Fork-first v3 release acceptance remains open until integrated CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant