Skip to content

Share spatial index validation between models and migrations - #334

Draft
nikitasavinov wants to merge 1 commit into
masterfrom
refactor/shared-spatial-index-validation
Draft

nikitasavinov wants to merge 1 commit into
masterfrom
refactor/shared-spatial-index-validation

Conversation

@nikitasavinov

Copy link
Copy Markdown
Owner

Spatial index restrictions were duplicated between design-time model validation and migration SQL generation. Both paths now call SpatialIndexAnnotation.ValidateIndex, removing 40 lines of production code while preserving the spatial type, bounding-box, primary-key, and SQL generation checks.

Expand the existing raw-operation test to cover clustered indexes, included columns, ONLINE, fill factor, tempdb sorting, and compression, including explicitly disabled unsupported options.

Validation: 132 tests passed with dotnet test --solution EntityFrameworkCore.Extensions.sln --configuration Release --no-restore; five SQL Server integration tests were skipped because no connection was configured. Formatting verification for all four changed files and git diff --check passed.

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