Groups change reasons into logical categories. More...
#include <change_reason_category.hpp>
Collaboration diagram for change_reason_category:
Public Attributes | |
| int | version = 0 |
| Version number for optimistic locking and change tracking. | |
| std::string | code |
| Unique code identifying this category. | |
| std::string | description |
| Human-readable description of the category's purpose. | |
| std::string | recorded_by |
| Username of the person who last modified this category. | |
| std::string | change_commentary |
| Free-text commentary explaining the change. | |
| std::chrono::system_clock::time_point | recorded_at |
| Timestamp when this version of the record was recorded. | |
Detailed Description
Groups change reasons into logical categories.
Change reason categories define the namespace for change reasons and determine which reasons apply to which entity types. Categories provide a way to organize change reasons by domain or purpose.
Examples of categories:
- static_data: For changes to reference data like currencies, countries
- trade: For trade-related modifications
- market_data: For market data corrections
- system: For system-level changes like initial creation
- Note
- This type only includes change_commentary (not change_reason_code) because this entity IS a change reason category. Self-referential tracking is handled at the database level.
Member Data Documentation
◆ code
| std::string code |
Unique code identifying this category.
This is the natural key for the category. Examples: "static_data", "trade", "market_data", "system".
