Repository navigation
Tags: CaffeinatedCoder/EFCore.ComplexIndexes
Tags
build: drop GeneratePackageOnBuild so `dotnet pack` builds first The SDK's pack targets prepend `Build` to GenerateNuspecDependsOn only when NoBuild != true AND GeneratePackageOnBuild != true, so setting the property silently turned every `dotnet pack` into a no-build pack of whatever happened to be sitting in bin/. Locally that is stale output from an earlier build — the packages would not necessarily have come from the committed source. On a clean checkout bin/ is empty and pack fails with NU5026, which is how the PR pack job found it. The release workflow was already safe by virtue of running an explicit `dotnet build` first, but only by accident of how it was written. Co-Authored-By: Claude Opus 5 <[email protected]>
v5.0.1: idempotent exclusion DDL, constraint rename normalization, sn… …apshot round-trip tests Response to the AuditOffice adoption review. The reported per-migration re-emission of exclusion constraints is not reproducible with a fresh build (verified through the real dotnet-ef pipeline and the decompiled published package — the symptom requires a stale compiled snapshot); the hardening here makes even that case harmless and fixes the review's genuine finding: - Exclusion ADD CONSTRAINT is preceded by DROP CONSTRAINT IF EXISTS, so adopting a same-named hand-written constraint applies without 42P07; standalone drops use IF EXISTS too. - Exclusion/temporal/temporal-FK descriptors on renamed tables are compared under their new table identity (no more drop/rebuild churn), and name-only changes emit ALTER TABLE … RENAME CONSTRAINT; dependent temporal FKs survive principal renames via name-insensitive comparison. - SnapshotRoundTripTests compile real generated snapshot C# with Roslyn and diff against it — the exact migrations-add source path — guarding exclusion, temporal, and index features against round-trip churn. - README: adoption story + troubleshooting note on stale compiled snapshots. Co-Authored-By: Claude Fable 5 <[email protected]>
Add support for PostgreSQL temporal foreign keys and enhance migratio… …n differ - Introduced `HasTemporalForeignKey` API for PostgreSQL 18 temporal foreign keys (`PERIOD` syntax). - Enhanced `NpgsqlComplexIndexMigrationsModelDiffer` with temporal foreign key operations and validation. - Updated internal annotations to handle temporal foreign keys (`DependentPeriod`, `PrincipalPeriod`, etc.). - Added comprehensive tests for various temporal foreign key scenarios. - Updated README with examples, restrictions, and usage of temporal FKs. - Bumped package version to 4.0.0.
PreviousNext