Wolverine.Polecat: inherit DatabaseSchemaName for durability storage (#3175)#3208
Merged
Conversation
…ge (#3175) Wolverine.Polecat's IntegrateWithWolverine fell back to the "wolverine" schema for the message-durability store when no MessageStorageSchemaName was set, ignoring the Polecat store's DatabaseSchemaName. So two Polecat services with distinct document schemas silently shared the same durability tables (dead letters, nodes/assignments, agent-restriction state). Wolverine.Marten already inherits the DocumentStore's DatabaseSchemaName; mirror that for Polecat so distinct-schema services are isolated by default. (Polecat's TransportSchemaName is currently vestigial — no SQL Server queue transport is configured by IntegrateWithWolverine — so only the message-store schema needed the fix.) Closes #3175 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 23, 2026
Closed
This was referenced Jun 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Wolverine.Polecat'sIntegrateWithWolverine()now defaults the message-durability storage schema to the Polecat store'sDatabaseSchemaNamewhen noMessageStorageSchemaNameis configured, mirroringWolverine.Marten.Why
Marten resolves the message-store schema as:
Polecat skipped the
store.Options.DatabaseSchemaNamestep and fell straight back to"wolverine". So two Polecat services with distinct document schemas (e.g.polecat_trips/polecat_repair_shop) silently landed in the same durability schema and shared their durability tables — dead letters, node/assignment state, agent-restriction state. (Found via CritterWatch #504.)This aligns Polecat with Marten: distinct-schema Polecat services are isolated by default; an explicit
MessageStorageSchemaNamestill wins.Note on
TransportSchemaNameThe issue also mentions
TransportSchemaName, but Polecat'sIntegrateWithWolverinedoesn't currently configure a SQL Server queue transport (unlike Marten's PostgreSQL transport), so that property is presently vestigial — there's nothing reading it. Only the message-store schema needed the fix. If/when a Polecat queue transport is added, it should inheritDatabaseSchemaNamethe same way.Closes #3175
🤖 Generated with Claude Code