Skip to content

Fix ISoftDeleted in-memory update and NodaTime index IMMUTABLE errors - #4124

Merged
jeremydmiller merged 2 commits into
masterfrom
fixes
Feb 11, 2026
Merged

jeremydmiller merged 2 commits into
masterfrom
fixes

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Summary

Closes #2924
Closes #2415

Test plan

  • New test delete_sets_ISoftDeleted_properties_on_in_memory_document verifies in-memory properties are updated
  • All 59 soft delete tests pass
  • New test can_index_noda_time_types verifies indexes can be created on NodaTime fields
  • All 12 NodaTime tests pass (including 2 previously broken query tests now fixed)

🤖 Generated with Claude Code

jeremydmiller and others added 2 commits February 10, 2026 22:07
When Delete<T>(T entity) is called on a document implementing ISoftDeleted,
the in-memory Deleted and DeletedAt properties are now set immediately.
Previously only the database was updated. Closes GH-2924

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Registers an IMemberSource in the NodaTime plugin that maps NodaTime types
to the existing mt_immutable_* PostgreSQL functions, fixing index creation
that previously failed with "functions in index expression must be marked
IMMUTABLE". Closes GH-2415

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jeremydmiller
jeremydmiller merged commit 191dd73 into master Feb 11, 2026
6 of 7 checks passed
@jeremydmiller
jeremydmiller deleted the fixes branch February 11, 2026 11:18
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.

Implementing ISoftDeleted should update properties when you call IDocumentSession.Delete<T>(T document) Can't index Noda Time types

1 participant