What problem does it solve? Tracking historical changes to dimension data in DuckDB requires manual handling of row versioning, expiration dates, and current-record flags, which is error-prone when written from scratch. ## Core Features & Use Cases - SCD Type 2 Table Design: Provides schema conventions with surrogate keys, business keys, validity dates, and is_current flags. - Two-Step MERGE Pattern: Guides the MERGE INTO statement (DuckDB v1.4.0+) to expire changed rows, soft-delete missing records, and insert new ones, followed by an INSERT for new versions. - Use Case: When building a dbt model or DuckDB SQL pipeline that must preserve the full history of entity attributes (e.g., customer locations or names) for audit trails and point-in-time analytics. ## Quick Start Ask the AI to implement an SCD Type 2 dimension table in DuckDB for your entity using the MERGE INTO pattern with begin_date, end_date, and is_current tracking.