custom_format_conditions
Purpose
Section titled “Purpose”The parent table for the type-dispatched condition system. Each row defines a condition belonging to a custom format and dispatches to exactly one of nine child tables based on the type column. The arr_type column scopes conditions to a specific arr application or to all (all).
Columns
Section titled “Columns”| Column | Type | Nullable | Default | Description |
|---|---|---|---|---|
id |
INTEGER | Yes | — | — |
custom_format_name |
VARCHAR(100) | No | — | — |
name |
VARCHAR(100) | No | — | — |
type |
VARCHAR(50) | No | — | — |
arr_type |
VARCHAR(20) | No | ‘all’ | ‘radarr’, ‘sonarr’, ‘all’ |
negate |
INTEGER | No | 0 | — |
required |
INTEGER | No | 0 | — |
created_at |
TEXT | No | CURRENT_TIMESTAMP | — |
updated_at |
TEXT | No | CURRENT_TIMESTAMP | — |
Relationships
Section titled “Relationships”References:
- custom_formats — custom_formats (custom_format_name)
Referenced by:
-
FOREIGN KEY (custom_format_name) REFERENCES custom_formats(name) ON DELETE CASCADE ON UPDATE CASCADE
Constraints
Section titled “Constraints”- Primary key: (id)
- Unique: UNIQUE(custom_format_name, name)
- Arr-type note:
arr_typeacceptsradarr,sonarr, orall. Lidarr-specific conditions use the same column when applicable; validate per arr type rather than assuming cross-arr parity.