Processes AccountCommandMap structures for atomic update of events and their associated accounts.

This module handles the update of accounts based on validated AccountCommandMap data within the Double Entry Ledger system. Unlike standard update event processors, this variant does not persist error states to the database, instead returning changesets with error details for client handling.

Key Features

• Account Processing: Handles update of accounts based on the event map's action
• Atomic Operations: Ensures all event and account changes are performed in a single database transaction
• Error Handling: Maps validation and dependency errors to appropriate changesets without persistence
• Optimistic Concurrency Control: Integrates with OCC patterns for safe concurrent processing
• Dependency Resolution: Locates original create events and their associated accounts

Processing Flow

1. Command Creation: Creates an Command record from the AccountCommandMap for audit purposes
2. Dependency Resolution: Locates the original create account event and its account
3. Account Update: Updates the account using the payload data
4. Command Completion: Marks the event as processed upon successful account update
5. Linking: Creates a link between the event and the updated account for traceability

Error Handling

The module provides comprehensive error handling:

• Command validation errors are mapped back to AccountCommandMap changesets
• Account validation errors are propagated to the event map payload
• Dependency errors (missing create events) are handled gracefully
• All errors are returned as changesets without database persistence
• Database transaction ensures atomicity (all-or-nothing)

Supported Actions

Currently supports:

• :update_account - Updates an existing account from AccountCommandMap payload

Usage

This module is designed for scenarios where error persistence should be managed externally, allowing clients to handle validation errors and retry logic according to their specific requirements.