Class MoveOutboxMessageToDeadLetter
Represents a data request to move an outbox message to the dead letter table in the Postgres database.
[NoTenantTerm(TenantConfinement.IdentityAddressed, "the post-claim mutation path: the drain has already claimed this row cross-tenant and moves it by its globally-unique message id. This store holds no tenant context to filter by - an outbox store reads no ambient tenant context and accepts a tenant only as an explicit argument - so the statement carries no tenant term, and a caller that supplies a message id it did not obtain from a claim reaches the row behind it. Isolation on this table is established where the row is written, by stamping tenant_id")]
public sealed class MoveOutboxMessageToDeadLetter : DataRequest<int>, IDataRequest<IDbConnection, int>, IDataRequest
- Inheritance
-
MoveOutboxMessageToDeadLetter
- Implements
- Inherited Members
Constructors
MoveOutboxMessageToDeadLetter(string, string, string, int, CancellationToken)
Initializes a new instance of the MoveOutboxMessageToDeadLetter class.
public MoveOutboxMessageToDeadLetter(string messageId, string outboxTableName, string deadLetterTableName, int sqlTimeOutSeconds, CancellationToken cancellationToken)
Parameters
messageIdstringThe unique identifier of the message to move.
outboxTableNamestringThe name of the outbox table.
deadLetterTableNamestringThe name of the dead letter table.
sqlTimeOutSecondsintThe SQL command timeout in seconds.
cancellationTokenCancellationTokenThe cancellation token.
Remarks
The copy-to-DLQ and delete target the globally-unique outbox message_id, which addresses exactly
one row, so no tenant predicate is applied: the drain is cross-tenant infrastructure and must always be
able to move the row it claimed, regardless of any ambient tenant context.
The tenant is nonetheless COPIED, as provenance. The delete leaves the dead-letter row as the only remaining record of the message, so a term this statement does not carry across is destroyed rather than merely unqueryable: an operator could no longer attribute the entry, and a redrive could no longer re-enter the partition the message came from. It is copied from the outbox row, whose tenant column is total, so the value is always present and is never inferred here.
This framework request binds its fixed primitive input and output schema without runtime emit. Replacing a known parameter value is observed at execution; custom parameter metadata, templates and output callbacks are not an extension contract. Custom IDataRequest implementations are unchanged.