pyconvexity 0.3.8.post7__py3-none-any.whl → 0.4.1__py3-none-any.whl

pyconvexity/data/schema/01_core_schema.sql

@@ -1,17 +1,16 @@
 -- ============================================================================
--- CORE ENERGY NETWORK SCHEMA
--- Essential tables for networks, components, and attributes
--- Optimized for atomic database operations
--- Version 2.1.0
+-- CORE ENERGY NETWORK SCHEMA (SIMPLIFIED)
+-- Single-network-per-file design for desktop SQLite
+-- Optimized for fast timeseries access and simple Rust/Python API
+-- Version 3.1.0 - Single network + Sparse scenarios + Raw timeseries
 -- ============================================================================
 
 -- ============================================================================
--- NETWORKS AND TIME MANAGEMENT
+-- NETWORK METADATA
 -- ============================================================================
 
--- Networks table - represents energy system models
-CREATE TABLE networks (
-    id INTEGER PRIMARY KEY AUTOINCREMENT,
+-- Network metadata - single row per database file
+CREATE TABLE network_metadata (
     name TEXT NOT NULL,
     description TEXT,
     
@@ -20,55 +19,26 @@ CREATE TABLE networks (
     time_end DATETIME NOT NULL,
     time_interval TEXT NOT NULL,  -- ISO 8601 duration (PT1H, PT30M, PT2H, etc.)
     
-    -- Unmet load flag
-    unmet_load_active BOOLEAN DEFAULT 1, -- 1 = true, 0 = false
+    -- Network-level flags
+    locked BOOLEAN DEFAULT 0,  -- Prevent accidental edits to base network
     
     -- Metadata
     created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    created_by TEXT,
     
     CONSTRAINT valid_time_range CHECK (time_end > time_start)
 );
 
-CREATE INDEX idx_networks_name ON networks(name);
-CREATE INDEX idx_networks_created_at ON networks(created_at);
-
 -- Network time periods - optimized storage using computed timestamps
--- Instead of storing 75k+ timestamp strings, we compute them from the time axis
--- This reduces storage from ~3.4MB to ~24 bytes per network
 CREATE TABLE network_time_periods (
-    network_id INTEGER NOT NULL,
     period_count INTEGER NOT NULL,      -- Total number of periods (e.g., 8760 for hourly year)
     start_timestamp INTEGER NOT NULL,   -- Unix timestamp of first period
     interval_seconds INTEGER NOT NULL,  -- Seconds between periods (3600 for hourly)
     
-    PRIMARY KEY (network_id),
-    
-    CONSTRAINT fk_time_periods_network 
-        FOREIGN KEY (network_id) REFERENCES networks(id) ON DELETE CASCADE,
     CONSTRAINT valid_period_count CHECK (period_count > 0),
     CONSTRAINT valid_interval CHECK (interval_seconds > 0)
 );
 
--- No additional indexes needed - primary key on network_id is sufficient
--- Timestamps are computed as: start_timestamp + (period_index * interval_seconds)
-
--- Network locks - prevents concurrent modifications
-CREATE TABLE network_locks (
-    id INTEGER PRIMARY KEY AUTOINCREMENT,
-    network_id INTEGER NOT NULL UNIQUE,
-    locked_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    locked_by TEXT NOT NULL,  -- Process/user identifier
-    lock_reason TEXT NOT NULL,  -- 'solving', 'importing', 'editing', etc.
-    
-    CONSTRAINT fk_network_locks_network 
-        FOREIGN KEY (network_id) REFERENCES networks(id) ON DELETE CASCADE
-);
-
-CREATE INDEX idx_network_locks_network ON network_locks(network_id);
-CREATE INDEX idx_network_locks_reason ON network_locks(lock_reason);
-
 -- ============================================================================
 -- CARRIERS - ENERGY TYPES
 -- ============================================================================
@@ -76,8 +46,7 @@ CREATE INDEX idx_network_locks_reason ON network_locks(lock_reason);
 -- Carriers table - energy carriers (electricity, gas, heat, etc.)
 CREATE TABLE carriers (
     id INTEGER PRIMARY KEY AUTOINCREMENT,
-    network_id INTEGER NOT NULL,
-    name TEXT NOT NULL,
+    name TEXT NOT NULL UNIQUE,
     
     -- Carrier properties from PyPSA reference
     co2_emissions REAL DEFAULT 0.0,  -- tonnes/MWh
@@ -85,44 +54,32 @@ CREATE TABLE carriers (
     nice_name TEXT,                  -- Display name  
     max_growth REAL DEFAULT NULL,    -- MW - can be infinite
     max_relative_growth REAL DEFAULT 0.0,  -- MW
+    curtailable BOOLEAN DEFAULT FALSE, -- Whether the carrier can be curtailed
     
     -- Metadata
     created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    
-    CONSTRAINT fk_carriers_network 
-        FOREIGN KEY (network_id) REFERENCES networks(id) ON DELETE CASCADE,
-    CONSTRAINT uq_carriers_network_name 
-        UNIQUE (network_id, name)
+    updated_at DATETIME DEFAULT CURRENT_TIMESTAMP
 );
 
-CREATE INDEX idx_carriers_network ON carriers(network_id);
-CREATE INDEX idx_carriers_name ON carriers(network_id, name);
-
 -- ============================================================================
 -- UNIFIED COMPONENT SYSTEM
 -- ============================================================================
 
 -- Components table - unified table for all network components
--- This is the single source of truth for component identity and relationships
 CREATE TABLE components (
     id INTEGER PRIMARY KEY AUTOINCREMENT,
-    network_id INTEGER NOT NULL,
-    component_type TEXT NOT NULL,  -- 'BUS', 'GENERATOR', 'LOAD', 'LINE', 'LINK', 'STORAGE_UNIT', 'STORE', 'UNMET_LOAD'
-    name TEXT NOT NULL,
+    component_type TEXT NOT NULL,  -- 'BUS', 'GENERATOR', 'LOAD', 'LINE', 'LINK', 'STORAGE_UNIT', 'STORE', 'UNMET_LOAD', 'CONSTRAINT', 'TRANSFORMER', 'SHUNT_IMPEDANCE'
+    name TEXT NOT NULL UNIQUE,
     
-    -- Geographic location (optional - not all components have physical locations)
-    -- Lines and links are connections between buses and don't have their own coordinates
+    -- Geographic location (optional)
     latitude REAL,
     longitude REAL,
+    geometry TEXT,      -- GeoJSON geometry (Point, LineString, Polygon, etc.)
     
-    -- Energy carrier reference (NULL for CONSTRAINT components)
+    -- Energy carrier reference
     carrier_id INTEGER,
     
-    -- Bus connections - simple column approach
-    -- For single connections (GENERATOR, LOAD, STORAGE_UNIT, STORE): use bus_id
-    -- For dual connections (LINE, LINK): use bus0_id and bus1_id
-    -- For buses: all are NULL (buses don't connect to other buses)
+    -- Bus connections
     bus_id INTEGER,     -- Single bus connection
     bus0_id INTEGER,    -- First bus for lines/links
     bus1_id INTEGER,    -- Second bus for lines/links
@@ -131,8 +88,6 @@ CREATE TABLE components (
     created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     
-    CONSTRAINT fk_components_network 
-        FOREIGN KEY (network_id) REFERENCES networks(id) ON DELETE CASCADE,
     CONSTRAINT fk_components_carrier 
         FOREIGN KEY (carrier_id) REFERENCES carriers(id),
     CONSTRAINT fk_components_bus 
@@ -141,141 +96,178 @@ CREATE TABLE components (
         FOREIGN KEY (bus0_id) REFERENCES components(id),
     CONSTRAINT fk_components_bus1 
         FOREIGN KEY (bus1_id) REFERENCES components(id),
-    CONSTRAINT uq_components_network_name 
-        UNIQUE (network_id, name),
     CONSTRAINT valid_component_type 
-        CHECK (component_type IN ('BUS', 'GENERATOR', 'LOAD', 'LINE', 'LINK', 'STORAGE_UNIT', 'STORE', 'UNMET_LOAD', 'CONSTRAINT')),
-    -- New constraint: carrier_id must be NOT NULL for all components except CONSTRAINT
-    CONSTRAINT valid_carrier_id 
-        CHECK (component_type != 'CONSTRAINT' OR carrier_id IS NULL)
-    -- Note: UNMET_LOAD uniqueness per bus is enforced in backend logic since SQLite doesn't support partial unique constraints
+        CHECK (component_type IN ('BUS', 'GENERATOR', 'LOAD', 'LINE', 'LINK', 'STORAGE_UNIT', 'STORE', 'UNMET_LOAD', 'CONSTRAINT', 'TRANSFORMER', 'SHUNT_IMPEDANCE'))
 );
 
--- Optimized indexes for atomic operations
-CREATE INDEX idx_components_network ON components(network_id);
+-- Essential indexes only
 CREATE INDEX idx_components_type ON components(component_type);
 CREATE INDEX idx_components_name ON components(name);
-CREATE INDEX idx_components_network_type ON components(network_id, component_type);
-CREATE INDEX idx_components_carrier ON components(carrier_id);
-CREATE INDEX idx_components_network_name ON components(network_id, name);  -- For fast lookups
-CREATE INDEX idx_components_location ON components(latitude, longitude);   -- For spatial queries
-CREATE INDEX idx_components_bus ON components(bus_id);                     -- For bus connections
-CREATE INDEX idx_components_bus0 ON components(bus0_id);                   -- For line/link connections
-CREATE INDEX idx_components_bus1 ON components(bus1_id);                   -- For line/link connections
+CREATE INDEX idx_components_bus ON components(bus_id);
+CREATE INDEX idx_components_bus0 ON components(bus0_id);
+CREATE INDEX idx_components_bus1 ON components(bus1_id);
 
 -- ============================================================================
 -- ATTRIBUTE VALIDATION SYSTEM
 -- ============================================================================
 
--- Attribute validation rules table - defines what attributes are valid for each component type
--- This enforces PyPSA attribute definitions at the database level
+-- Attribute validation rules table
 CREATE TABLE attribute_validation_rules (
     id INTEGER PRIMARY KEY AUTOINCREMENT,
     component_type TEXT NOT NULL,
     attribute_name TEXT NOT NULL,
-    display_name TEXT,                 -- Human-readable display name
+    display_name TEXT,
     
-    -- Validation rules from PyPSA reference
+    -- Validation rules
     data_type TEXT NOT NULL,           -- 'float', 'boolean', 'string', 'int'
-    unit TEXT,                         -- 'MW', 'per unit', 'currency/MWh', etc.
-    default_value TEXT,                -- String representation of default
+    unit TEXT,
+    default_value TEXT,
     allowed_storage_types TEXT NOT NULL, -- 'static', 'timeseries', 'static_or_timeseries'
     is_required BOOLEAN DEFAULT FALSE,
-    is_input BOOLEAN DEFAULT TRUE,     -- TRUE for inputs, FALSE for outputs
+    is_input BOOLEAN DEFAULT TRUE,
     description TEXT,
     
-    -- Validation constraints
-    min_value REAL,                    -- Optional minimum value constraint
-    max_value REAL,                    -- Optional maximum value constraint
-    allowed_values TEXT,               -- JSON array of allowed values for string types
-    
-    -- Attribute grouping and storage control
-    group_name TEXT DEFAULT 'other',   -- Attribute group: 'basic', 'power', 'economics', 'control', 'other'
-    to_save BOOLEAN DEFAULT TRUE,      -- Whether to save this attribute in solve results
+    -- Constraints
+    min_value REAL,
+    max_value REAL,
+    allowed_values TEXT,  -- JSON array
     
-    -- Metadata
-    created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
+    -- Grouping
+    group_name TEXT DEFAULT 'other',
+    to_save BOOLEAN DEFAULT TRUE,
     
-    -- Constraints
     CONSTRAINT uq_validation_rule 
         UNIQUE (component_type, attribute_name),
     CONSTRAINT valid_component_type_validation 
-        CHECK (component_type IN ('BUS', 'GENERATOR', 'LOAD', 'LINE', 'LINK', 'STORAGE_UNIT', 'STORE', 'UNMET_LOAD', 'CONSTRAINT')),
+        CHECK (component_type IN ('BUS', 'GENERATOR', 'LOAD', 'LINE', 'LINK', 'STORAGE_UNIT', 'STORE', 'UNMET_LOAD', 'CONSTRAINT', 'TRANSFORMER', 'SHUNT_IMPEDANCE')),
     CONSTRAINT valid_data_type 
         CHECK (data_type IN ('float', 'boolean', 'string', 'int')),
     CONSTRAINT valid_allowed_storage_types 
         CHECK (allowed_storage_types IN ('static', 'timeseries', 'static_or_timeseries')),
     CONSTRAINT valid_group_name 
-        CHECK (group_name IN ('basic', 'power', 'economics', 'control', 'other'))
+        CHECK (group_name IN ('basic', 'capacity', 'power_limits', 'energy', 'unit_commitment', 'ramping', 'costs', 'electrical'))
 );
 
--- Optimized indexes for validation lookups
+-- Essential indexes only
 CREATE INDEX idx_validation_component_type ON attribute_validation_rules(component_type);
-CREATE INDEX idx_validation_attribute ON attribute_validation_rules(component_type, attribute_name);
-CREATE INDEX idx_validation_input ON attribute_validation_rules(is_input);
-CREATE INDEX idx_validation_required ON attribute_validation_rules(is_required);
+CREATE INDEX idx_validation_lookup ON attribute_validation_rules(component_type, attribute_name);
 
 -- ============================================================================
--- UNIFIED COMPONENT ATTRIBUTES
+-- SCENARIOS - SPARSE OVERRIDE APPROACH
 -- ============================================================================
 
--- Component attributes - unified storage for all component properties
--- This is the heart of our atomic attribute system with scenario support
+-- Scenarios table - represents alternative scenarios
+-- Base network has NO scenario (scenario_id = NULL in attributes)
+-- Supports both deterministic what-if scenarios (probability = NULL) and stochastic scenarios (probability set)
+CREATE TABLE scenarios (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    name TEXT NOT NULL UNIQUE,
+    description TEXT,
+    probability REAL DEFAULT NULL,  -- For stochastic optimization (NULL = deterministic what-if)
+    created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
+    
+    CONSTRAINT valid_probability 
+        CHECK (probability IS NULL OR (probability >= 0 AND probability <= 1))
+);
+
+-- ============================================================================
+-- UNIFIED COMPONENT ATTRIBUTES - SPARSE SCENARIOS + RAW TIMESERIES
+-- ============================================================================
+
+-- Component attributes - sparse scenario overrides
+-- scenario_id = NULL → Base network (editable)
+-- scenario_id = 1    → Scenario 1 (overrides base, read-only)
 CREATE TABLE component_attributes (
     id INTEGER PRIMARY KEY AUTOINCREMENT,
     component_id INTEGER NOT NULL,
     attribute_name TEXT NOT NULL,
     
-    -- Scenario support - references scenarios table (master scenario has explicit ID)
-    scenario_id INTEGER NOT NULL,
+    -- Scenario support - NULL = base network, non-NULL = scenario override
+    scenario_id INTEGER,  -- NULLABLE!
     
-    -- Storage type - determines how value is stored
+    -- Storage type
     storage_type TEXT NOT NULL CHECK (storage_type IN ('static', 'timeseries')),
     
-    -- Unified value storage - exactly one must be non-NULL based on storage_type
-    static_value TEXT,               -- JSON-encoded static value (handles all data types)
-    timeseries_data BLOB,           -- Parquet format for timeseries
+    -- Value storage
+    static_value TEXT,      -- JSON-encoded static value (all data types)
+    timeseries_data BLOB,   -- Raw f32 array (NOT Parquet!)
     
-    -- Cached metadata for performance
-    data_type TEXT NOT NULL,        -- Copied from validation rules for fast access
-    unit TEXT,                      -- Copied from validation rules for fast access
-    is_input BOOLEAN DEFAULT TRUE,  -- Copied from validation rules for fast access
+    -- Cached metadata
+    data_type TEXT NOT NULL,
+    unit TEXT,
+    is_input BOOLEAN DEFAULT TRUE,
     
     -- Metadata
     created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     
-    -- Constraints
     CONSTRAINT fk_attributes_component 
         FOREIGN KEY (component_id) REFERENCES components(id) ON DELETE CASCADE,
     CONSTRAINT fk_attributes_scenario 
         FOREIGN KEY (scenario_id) REFERENCES scenarios(id) ON DELETE CASCADE,
     
-    -- Ensure exactly one storage type is used
+    -- Storage validation
     CONSTRAINT check_exactly_one_storage_type CHECK (
         (storage_type = 'static' AND static_value IS NOT NULL AND timeseries_data IS NULL) OR
         (storage_type = 'timeseries' AND static_value IS NULL AND timeseries_data IS NOT NULL)
     ),
     
-    -- Ensure unique attribute per component per scenario
+    -- Unique per component/attribute/scenario (NULL scenario counts as unique value)
     CONSTRAINT uq_component_attribute_scenario 
         UNIQUE (component_id, attribute_name, scenario_id)
 );
 
--- Highly optimized indexes for atomic operations with scenario support
-CREATE INDEX idx_attributes_component ON component_attributes(component_id);
-CREATE INDEX idx_attributes_name ON component_attributes(attribute_name);
-CREATE INDEX idx_attributes_storage_type ON component_attributes(storage_type);
-CREATE INDEX idx_attributes_component_name ON component_attributes(component_id, attribute_name);
-CREATE INDEX idx_attributes_data_type ON component_attributes(data_type);
-CREATE INDEX idx_attributes_is_input ON component_attributes(is_input);
+-- Essential indexes only
+CREATE INDEX idx_attributes_lookup ON component_attributes(
+    component_id, attribute_name, scenario_id
+);
 CREATE INDEX idx_attributes_scenario ON component_attributes(scenario_id);
 
--- Composite indexes for common query patterns
-CREATE INDEX idx_attributes_component_input ON component_attributes(component_id, is_input);
-CREATE INDEX idx_attributes_component_storage ON component_attributes(component_id, storage_type);
-CREATE INDEX idx_attributes_component_scenario ON component_attributes(component_id, scenario_id);
+-- ============================================================================
+-- SCENARIO CACHE - MATERIALIZED VIEW FOR FAST SCENARIO COUNTING
+-- ============================================================================
+
+-- Scenario cache - stores precomputed scenario counts and details
+-- This is a materialized view that's kept in sync via application code
+-- Updated transactionally whenever attribute values change
+CREATE TABLE IF NOT EXISTS attribute_scenario_cache (
+    component_id INTEGER NOT NULL,
+    attribute_name TEXT NOT NULL,
+    
+    -- Cached computed values
+    scenario_count INTEGER NOT NULL DEFAULT 1,      -- Display count (includes synthetic base)
+    has_base_value BOOLEAN NOT NULL DEFAULT FALSE,  -- TRUE if base network has value
+    has_scenario_values BOOLEAN NOT NULL DEFAULT FALSE, -- TRUE if any scenarios have values
+    
+    -- Scenario details for dropdown (JSON array)
+    -- Format: [{scenario_id: 0, scenario_name: "Base", value: "123", has_value: true}, ...]
+    scenario_details TEXT,
+    
+    -- Metadata
+    last_updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
+    
+    PRIMARY KEY (component_id, attribute_name),
+    CONSTRAINT fk_scenario_cache_component 
+        FOREIGN KEY (component_id) REFERENCES components(id) ON DELETE CASCADE
+);
+
+-- Index for fast component-based lookups
+CREATE INDEX IF NOT EXISTS idx_scenario_cache_component 
+    ON attribute_scenario_cache(component_id);
+
+-- Index for bulk table loads
+CREATE INDEX IF NOT EXISTS idx_scenario_cache_component_type
+    ON attribute_scenario_cache(component_id, attribute_name);
+
+-- NOTES:
+-- This cache is maintained by application code (Rust) in the same transaction
+-- as attribute writes. This ensures ACID guarantees - the cache can never be
+-- stale or inconsistent with the actual data.
+--
+-- Cache logic:
+-- - If has_scenario_values: scenario_count = num_scenarios + 1 (always include base)
+-- - If only has_base_value: scenario_count = 1 (no indicator shown)
+-- - If neither: scenario_count = 0 (no values at all)
 
 -- ============================================================================
 -- VALIDATION TRIGGERS
@@ -311,37 +303,7 @@ BEGIN
     SELECT RAISE(ABORT, 'Storage type not allowed for this attribute');
 END;
 
--- Trigger to validate attributes against rules on update
-CREATE TRIGGER validate_component_attribute_update
-    BEFORE UPDATE ON component_attributes
-    FOR EACH ROW
-    WHEN NOT EXISTS (
-        SELECT 1 FROM components c
-        JOIN attribute_validation_rules avr ON c.component_type = avr.component_type
-        WHERE c.id = NEW.component_id 
-        AND avr.attribute_name = NEW.attribute_name
-    )
-BEGIN
-    SELECT RAISE(ABORT, 'Attribute is not defined for this component type');
-END;
-
--- Trigger to validate storage type on update
-CREATE TRIGGER validate_storage_type_update
-    BEFORE UPDATE ON component_attributes
-    FOR EACH ROW
-    WHEN EXISTS (
-        SELECT 1 FROM components c
-        JOIN attribute_validation_rules avr ON c.component_type = avr.component_type
-        WHERE c.id = NEW.component_id
-        AND avr.attribute_name = NEW.attribute_name
-        AND avr.allowed_storage_types != 'static_or_timeseries'
-        AND avr.allowed_storage_types != NEW.storage_type
-    )
-BEGIN
-    SELECT RAISE(ABORT, 'Storage type not allowed for this attribute');
-END;
-
--- Trigger to update metadata timestamps
+-- Trigger to update timestamps
 CREATE TRIGGER update_component_attributes_timestamp
     BEFORE UPDATE ON component_attributes
     FOR EACH ROW
@@ -361,100 +323,38 @@ BEGIN
     WHERE id = NEW.component_id;
 END;
 
--- ============================================================================
--- COMPONENT GEOMETRIES - Optional GeoJSON geometries for spatial representation
--- ============================================================================
-
--- Component geometries - stores optional GeoJSON geometries for components
--- Enables real spatial representation (e.g., actual line routes, generator footprints)
-CREATE TABLE component_geometries (
-    id INTEGER PRIMARY KEY AUTOINCREMENT,
-    component_id INTEGER NOT NULL UNIQUE,
-    
-    -- GeoJSON geometry stored as JSON text
-    -- Supports: Point, LineString, Polygon, MultiPolygon, MultiPoint, MultiLineString, GeometryCollection
-    geometry TEXT NOT NULL,
-    
-    -- Cache the geometry type for faster queries and validation
-    geometry_type TEXT NOT NULL CHECK (geometry_type IN (
-        'Point', 'LineString', 'Polygon', 'MultiPolygon', 
-        'MultiPoint', 'MultiLineString', 'GeometryCollection'
-    )),
-    
-    -- Cache bounding box for spatial indexing and quick filtering
-    bbox_min_lng REAL,
-    bbox_min_lat REAL,
-    bbox_max_lng REAL,
-    bbox_max_lat REAL,
-    
-    -- Metadata
-    created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
-    
-    CONSTRAINT fk_geometry_component 
-        FOREIGN KEY (component_id) REFERENCES components(id) ON DELETE CASCADE
-);
-
--- Indexes for efficient geometry queries
-CREATE INDEX idx_component_geometries_component ON component_geometries(component_id);
-CREATE INDEX idx_component_geometries_type ON component_geometries(geometry_type);
-CREATE INDEX idx_component_geometries_bbox ON component_geometries(
-    bbox_min_lng, bbox_min_lat, bbox_max_lng, bbox_max_lat
-);
-
--- Trigger to update timestamp on geometry changes
-CREATE TRIGGER update_component_geometries_timestamp
-    BEFORE UPDATE ON component_geometries
-    FOR EACH ROW
-BEGIN
-    UPDATE component_geometries 
-    SET updated_at = CURRENT_TIMESTAMP 
-    WHERE id = NEW.id;
-END;
-
 -- ============================================================================
 -- NETWORK CONFIGURATION
 -- ============================================================================
 
--- Network configuration parameters - flexible parameter storage
--- Supports scenario-aware configuration with fallback to network defaults
+-- Network configuration parameters with scenario support
 CREATE TABLE network_config (
     id INTEGER PRIMARY KEY AUTOINCREMENT,
-    network_id INTEGER NOT NULL,
     scenario_id INTEGER, -- NULL for network defaults
     
-    -- Parameter definition
     param_name TEXT NOT NULL,
     param_type TEXT NOT NULL,
     param_value TEXT NOT NULL,
     param_description TEXT,
     
-    -- Metadata
     created_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     updated_at DATETIME DEFAULT CURRENT_TIMESTAMP,
     
-    CONSTRAINT fk_network_config_network 
-        FOREIGN KEY (network_id) REFERENCES networks(id) ON DELETE CASCADE,
     CONSTRAINT fk_network_config_scenario 
         FOREIGN KEY (scenario_id) REFERENCES scenarios(id) ON DELETE CASCADE,
     CONSTRAINT uq_network_config_param 
-        UNIQUE (network_id, scenario_id, param_name),
+        UNIQUE (scenario_id, param_name),
     CONSTRAINT valid_param_type 
         CHECK (param_type IN ('boolean', 'real', 'integer', 'string', 'json'))
 );
 
--- Indexes for performance
-CREATE INDEX idx_network_config_network ON network_config(network_id);
-CREATE INDEX idx_network_config_scenario ON network_config(scenario_id);
-CREATE INDEX idx_network_config_param ON network_config(param_name);
-CREATE INDEX idx_network_config_network_param ON network_config(network_id, param_name);
-CREATE INDEX idx_network_config_network_scenario_param ON network_config(network_id, scenario_id, param_name);
+CREATE INDEX idx_network_config_lookup ON network_config(scenario_id, param_name);
 
 -- ============================================================================
 -- SYSTEM METADATA
 -- ============================================================================
 
--- System metadata table for schema versioning and configuration
+-- System metadata table for schema version tracking and system-level settings
 CREATE TABLE system_metadata (
     id INTEGER PRIMARY KEY AUTOINCREMENT,
     key TEXT NOT NULL UNIQUE,
@@ -466,12 +366,12 @@ CREATE TABLE system_metadata (
 
 CREATE INDEX idx_system_metadata_key ON system_metadata(key);
 
--- Insert initial schema version
+-- Initialize system metadata with schema version
 INSERT INTO system_metadata (key, value, description) 
-VALUES ('schema_version', '2.4.0', 'Database schema version - Added network_config table for flexible parameter storage');
+VALUES ('schema_version', '3.1.0', 'Database schema version');
 
-INSERT INTO system_metadata (key, value, description) 
-VALUES ('created_at', datetime('now'), 'Database creation timestamp');
+-- ============================================================================
+-- SCHEMA VERSION
+-- ============================================================================
 
-INSERT INTO system_metadata (key, value, description) 
-VALUES ('atomic_operations', 'enabled', 'Atomic database operations support'); 
+PRAGMA user_version = 31;  -- Schema version 3.1