ores.refdata.calendar_event

One row per dated diary entry on a calendar: a central-bank meeting, a scheduled data release, or an open-ended other event. One table for all event kinds – never a table per calendar or per type (settled 2026-08-09, story Decision D1; see Calendar Events). The diary_entry_type column classifies the entry via the open-ended diary_entry_type vocabulary (holiday, central_bank_meeting, data_release, other). Holidays themselves keep their existing machinery (calendar_rules, calendar_exceptions, calendar_date) – the holiday type stays in the vocabulary so the whole classification lives in one place, even though its physical home is elsewhere.

Template/Instance: an event row is an instance; its template is the (calendar, diary_entry_type, name) triple. A worked case: the FOMC's eight regularly scheduled meetings per year are entered as a short run of central_bank_meeting instances on the US.FOMC calendar, transcribed from the Fed's published calendar with source'federalreserve.gov'. Formulaic recurrence generation is deferred; =calendar_rules's grammar can later feed a template link if a consumer needs it.

std::string("TARGET")

std::chrono::year_month_day{std::chrono::floor<std::chrono::days>(ctx.past_timepoint())}

std::string("holiday")

std::string("Test event")

std::string("Test event description")

std::string("federalreserve.gov")

#include <boost/uuid/uuid.hpp>
#include <chrono>
#include <optional>
#include <string>

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