[sadeqabuhattem]

Composing this library with DotNetBoost.Auditing in one DbContext (in dotnetboost-sample) raised questions the suite could not answer: nothing ran the save interceptor next to another interceptor that saves again once a save completes. This branch adds those tests, fixes what they found, and records the rest in COMPOSITION-GAPS.md.

The library takes no dependency on any other DotNetBoost library. The tests use a test-only interceptor shaped like Auditing's deferred pass.

Fixed

• A save issued by another interceptor from inside ours wiped ours (gap 1). An interceptor registered before UseMultiLingual runs its SavedChanges first. A SaveChanges it issued there restarted this interceptor's save: the outer save's translation deletes were lost, and its transaction was committed from inside the nested save. Saves are now counted per context. A nested one joins the outer save, and only the outermost completion writes, commits or rolls back. A save EF never reported as finished (an interceptor's SavingChanges threw) is not mistaken for one still in flight.
• An interceptor registered after UseMultiLingual did its post-save work outside the transaction (gap 2). When another SaveChanges interceptor follows this one, the commit now waits for EF's DbContext.SavedChanges event. On EF 8 and 10 that event fires once every interceptor's SavedChanges has returned, and not at all when one throws. That commit is synchronous, because the event is, and it is deferred only on such a context.
• A concurrency conflict or a cancelled save left the owned transaction open. EF reports neither through SaveChangesFailed, only through ThrowingConcurrencyException and SaveChangesCanceled, which are now handled.
• A rolled-back save left rows another interceptor added during it tracked, under rolled-back keys, so retrying the save on the same context failed on a duplicate key.

Added

• .OwnTransactions(bool) (EF Core, default true). With false, the application owns the transaction, and a save that writes translations without one is refused before anything is written.
• Docs:
  • Sharing a DbContext with other SaveChanges interceptors in docs/limitations.md: what each hook does and what to do per setup. It also says why EF's usual acceptAllChangesOnSuccess: false retry pattern breaks beside an interceptor that saves again: the second save inserted a row twice.
  • A checklist for storing text about another library's entity, in docs/reading-and-writing.md.

Still open

• A retrying strategy with the other interceptor registered first. The commit has to happen inside the strategy's own call, so it cannot wait for the event. The docs say to register UseMultiLingual first there. These are the skipped test rows.
• Gap 3 (SetAll / GetAllAsync(includeBase: true)) and the rest of gap 4 are features. They will come on their own branches.

Testing

• SaveCompositionTests and SyncSaveCompositionTests (SQLite) cover every case with the other interceptor registered before and after UseMultiLingual, each with and without a retrying strategy, async and sync.

• SaveCompositionIntegrationTests runs the core of the matrix on PostgreSQL 17 and SQL Server 2022, with each provider's own EnableRetryOnFailure.

• To check the tests depend on each fix, I removed each fix in turn, and its tests failed:

  • with the nesting check removed, the refused-save cases fail;
  • with the deferral off, exactly the "registered after" rows fail;
  • with the sync hooks broken, only sync tests fail.

• Results on net8.0 and net10.0:

  Suite	Passed	Skipped
  Unit	227	0
  Provider	290	6
  API	55 / 56	0
  Integration	196	6

  The skipped rows are the open case above.

🤖 Generated with Claude Code