docs: align analytics with growth capability
This commit is contained in:
@@ -98,7 +98,7 @@ Unique `(import_run_id, severity, rule_code)` keeps one aggregate record per rul
|
||||
| `reporting_week_end_exclusive` | `date` required | following Saturday; equals start + 7 days |
|
||||
| `persian_season` | `smallint` required | `1..4` |
|
||||
|
||||
Unique `(jalali_year, jalali_month, jalali_day)` prevents duplicate calendar mappings. Indexes on `(jalali_year, jalali_month, gregorian_date)`, `(jalali_year, persian_season, gregorian_date)`, and `(reporting_week_start, gregorian_date)` support approved periods. Holiday/named-event columns do not exist.
|
||||
Unique `(jalali_year, jalali_month, jalali_day)` prevents duplicate calendar mappings. Indexes on `(jalali_year, jalali_month, gregorian_date)`, `(jalali_year, persian_season, gregorian_date)`, and `(reporting_week_start, gregorian_date)` support approved periods. Holiday/named-event columns do not exist here; the later growth capability owns a separate reviewed event-evidence catalog.
|
||||
|
||||
### Merchant and demo identity
|
||||
|
||||
|
||||
Reference in New Issue
Block a user