ores.refdata.calendar_name
Table of Contents
ORE names a calendar by text, and its schema fixes the names it accepts: 471
of them, such as TARGET, US settlement, weekends only and currency codes
that stand for a currency's calendar. The schema also accepts two open forms
no list can hold – any four-letter exchange code such as XNYS, and any name
beginning CUSTOM_ – and joins of several calendars, written as TARGET,UK
or JoinHolidays(TARGET, US settlement).
A curve keeps the calendar expression its document wrote, so the export writes
it back unchanged. ores_refdata_validate_calendar_fn splits the expression
and checks each calendar in it against this table or against one of the two
open forms, so a calendar ORE would refuse is refused on insert. The refdata
calendar table models calendars the system materialises; this table is the
vocabulary of names an ORE document may write.
1. Flags
2. Columns
2.1. code
The calendar name exactly as an ORE document may write it: 'TARGET', 'US settlement', 'weekends only', 'USD'.
std::string("TARGET")
2.2. description
What the spelling means, in one line, for a reader who does not know ORE.
std::string(faker::lorem::sentence())
3. SQL
3.1. Flags
4. C++
4.1. Flags
4.2. Repository
4.3. Domain includes
#include <string>
4.4. Conventions
4.5. Presentation
4.5.1. Detail fields
| field | label | widget | type | is_key | is_required | placeholder |
|---|---|---|---|---|---|---|
| code | Code | codeEdit | line_edit | true | true | e.g. TARGET |
| description | Description | descriptionEdit | text_edit | Enter a description |
4.5.2. Columns
| enum_name | field | header | type | width |
|---|---|---|---|---|
| Code | code | Code | string | 200 |
| Description | description | Description | string | 350 |
| Version | version | Version | int | 80 |
| ModifiedBy | modified_by | Modified By | string | 120 |
| RecordedAt | recorded_at | Recorded At | timestamp | 150 |
4.6. Custom repository methods
5. See also
- ores.refdata — component group overview.