Skip to content

Fix PostgreSQL clone fixture user ownership - #497

Merged
stef-k merged 2 commits into
mainfrom
fix/495-postgres-clone-fixture
Aug 22, 2026
Merged

Fix PostgreSQL clone fixture user ownership#497
stef-k merged 2 commits into
mainfrom
fix/495-postgres-clone-fixture

Conversation

@stef-k

@stef-k stef-k commented Aug 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • attach the already-persisted API user to the clone fixture context before creating its required token navigation
  • prevent EF Core from treating that detached user as a new AspNetUsers row
  • preserve the complete guarded PostgreSQL clone, rollback, and cleanup assertions

Closes #495.

Validation

  • immutable red checkpoint: duplicate PK_AspNetUsers failure reproduced
  • corrected guarded PostgreSQL clone workflow: 1 passed, 0 failed/skipped
  • PostgreSQL environment/residue evidence: 1 passed, 0 failed/skipped
  • related TripClone selection: 4 passed, 0 failed/skipped
  • Release test/application build: succeeded, 0 warnings/errors
  • LOC policy: passed; pre-existing warnings only
  • git diff --check: passed

Database

No migration or production database change. Test-fixture ownership correction only.

@stef-k
stef-k merged commit a64c8f0 into main Aug 22, 2026
1 check passed
@stef-k stef-k mentioned this pull request Aug 22, 2026
@stef-k
stef-k deleted the fix/495-postgres-clone-fixture branch August 22, 2026 21:04
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.

Fix detached API user ownership in PostgreSQL clone fixture

1 participant