ores.dq.badge_mapping

Table of Contents

Universal mapping table that associates any (code_domain, entity_code) pair with a badge definition. This is the single join point between domain values and their visual presentation.

Examples:

Populated via seed scripts; no management UI needed.

NATS/protocol/service are disabled above: badge lookups already go through the hand-maintained badge_handler=/=badge_service (see registrar.cpp's own comment), so the generic generated messaging stack for this junction would be dead code alongside it.

Flags

Left

Code of the domain this mapping belongs to.

References code_domain.code (soft FK). Examples: 'party_status', 'fsm_state'.

std::string(faker::word::noun()) + "_status"

Right

The domain value being mapped to a badge.

Examples: 'ACTIVE', 'DRAFT', 'Online', 'Actual'.

std::string(faker::word::adjective()).substr(0, 1)

Columns

badge_code

The badge definition to use for this mapping.

References badge_definition.code (soft FK). Examples: 'active', 'fsm_draft'.

std::string(faker::word::adjective())

SQL

Flags

Repository

C++

Flags

Domain includes

#include <chrono>
#include <string>

Entity includes

#include <string>
#include "sqlgen/Timestamp.hpp"
#include "sqlgen/PrimaryKey.hpp"

Conventions

Table display

column header
code_domain_code Code Domain
entity_code Entity Code
badge_code Badge
modified_by Modified By
version Version

See also

  • ores.dq — component group overview.

Emacs 29.3 (Org mode 9.6.15)