Skip to content

Fix MSSQL apply order and compare for NAV-style object names - #68

Merged
aersam merged 2 commits into
mainfrom
64-nav-style-names
Oct 31, 2026
Merged

aersam merged 2 commits into
mainfrom
64-nav-style-names

Conversation

@aersam

@aersam aersam commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Part of #64 (item 3), bumps to 0.17.2.

Found by running a NAV-like schema (names like [Company$Cust_ Ledg_ Entry é]) through apply, introspect and compare on a real SQL Server:

  • Apply order: dependency names were re-quoted by exp.table_name and never matched the file-derived names, so views were applied before their tables.
  • compare: decimal(38,20) vs numeric(38, 20), bracket-quoted index columns, index names with spaces, and nested-paren filters (([b]>(1))) gave false diffs.

Measured with 1,950 tables and 4,500 views: apply 17 s, parse 2.3 s, introspect 6.4 s, diff 0.4 s, 98 MB RSS, 0 diffs. Introspection runs several queries per table, so against a remote server it is latency-bound (not changed). Views are introspected and compared; update-stats quotes names correctly (live test added).

🤖 Generated with Claude Code

Claude Session: 928b2739-5a21-5fd4-b2a1-23bb76c373be

@aersam
aersam merged commit b63face into main Oct 31, 2026
2 checks passed
aersam and others added 2 commits October 31, 2026 08:08
…accents (#64)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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