kasl/db/

migrations.rs

//! Database schema migration management and versioning system.
//!
//! Provides a comprehensive migration framework for evolving the database schema
//! over time while maintaining data integrity and consistency.
//!
//! ## Usage
//!
//! ```rust,no_run
//! # fn main() -> Result<(), Box<dyn std::error::Error>> {
//! use kasl::db::migrations::{init_with_migrations, get_db_version};
//! use rusqlite::Connection;
//!
//! let mut conn = Connection::open("kasl.db")?;
//! init_with_migrations(&mut conn)?;
//! let version = get_db_version(&conn)?;
//! # Ok(())
//! # }
//! ```

use crate::libs::messages::Message;
use crate::{msg_debug, msg_error, msg_info, msg_success};
use anyhow::Result;
use rusqlite::{Connection, Transaction, params};

/// SQL schema for the migrations tracking table.
///
/// This table maintains a complete record of all applied migrations,
/// enabling version tracking and providing an audit trail of schema changes.
/// Each migration is recorded with its version, name, and application timestamp.
const MIGRATIONS_TABLE: &str = "
CREATE TABLE IF NOT EXISTS migrations (
    id INTEGER PRIMARY KEY,
    version INTEGER NOT NULL UNIQUE,
    name TEXT NOT NULL,
    applied_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
)";

/// Represents a single database migration with execution logic.
///
/// Each migration contains the information needed to apply a specific
/// schema change, including version tracking and the transformation function.
/// Migrations are designed to be immutable and deterministic.
#[derive(Debug, Clone)]
struct Migration {
    /// Unique version number for ordering and tracking
    version: u32,
    /// Human-readable name describing the migration's purpose
    name: &'static str,
    /// Function that applies the schema changes within a transaction
    up: fn(&Transaction) -> Result<()>,
}

/// Central migration system manager that orchestrates schema evolution.
///
/// The `MigrationManager` maintains the complete registry of available migrations
/// and provides the logic for applying them in the correct order. It ensures
/// that migrations are applied atomically and tracks their completion status.
pub struct MigrationManager {
    /// Ordered list of all available migrations
    ///
    /// Migrations are stored in version order to ensure correct application
    /// sequence. Each migration builds upon the schema state created by
    /// its predecessors.
    migrations: Vec<Migration>,
}

impl Default for MigrationManager {
    fn default() -> Self {
        Self::new()
    }
}

impl MigrationManager {
    /// Creates a new migration manager with all registered migrations.
    ///
    /// # Example
    ///
    /// ```rust
    /// use kasl::db::migrations::MigrationManager;
    ///
    /// let manager = MigrationManager::new();
    /// // Manager is ready to apply migrations
    /// ```
    pub fn new() -> Self {
        let mut manager = Self { migrations: Vec::new() };

        // Register all migrations in chronological order
        // Each registration adds a migration to the internal registry
        manager.register_migrations();
        manager
    }

    /// Registers all database migrations in chronological order.
    fn register_migrations(&mut self) {
        // Initial schema - version 0 is implicit (empty database)
        // Base tables are created by individual modules as needed

        // Version 1: Base tables and performance indices
        // Creates fundamental tables and adds indices for better performance
        self.add_migration(1, "create_tables_and_indices", |tx| {
            // First, create base tables that individual modules depend on
            // This ensures tables exist before any indices are created

            // Create tasks table
            tx.execute(
                "CREATE TABLE IF NOT EXISTS tasks (
        id INTEGER NOT NULL PRIMARY KEY,
        task_id INTEGER NOT NULL ON CONFLICT REPLACE DEFAULT 0,
        timestamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
        name TEXT NOT NULL,
        comment TEXT,
        completeness INTEGER NOT NULL ON CONFLICT REPLACE DEFAULT 100,
        excluded_from_search BOOLEAN NOT NULL ON CONFLICT REPLACE DEFAULT FALSE
    )",
                [],
            )?;

            // Create pauses table
            tx.execute(
                "CREATE TABLE IF NOT EXISTS pauses (
        id INTEGER NOT NULL PRIMARY KEY,
        start TIMESTAMP NOT NULL,
        end TIMESTAMP,
        duration INTEGER
    )",
                [],
            )?;

            // Create workdays table
            tx.execute(
                "CREATE TABLE IF NOT EXISTS workdays (
        id INTEGER PRIMARY KEY,
        date DATE NOT NULL UNIQUE,
        start TIMESTAMP NOT NULL,
        end TIMESTAMP
    )",
                [],
            )?;

            // Now create indices for the tables we just created

            // Index tasks by timestamp for chronological queries
            tx.execute("CREATE INDEX IF NOT EXISTS idx_tasks_timestamp ON tasks(timestamp)", [])?;
            // Index tasks by parent task relationship
            tx.execute("CREATE INDEX IF NOT EXISTS idx_tasks_task_id ON tasks(task_id)", [])?;
            // Index pauses by start time for temporal queries
            tx.execute("CREATE INDEX IF NOT EXISTS idx_pauses_start ON pauses(start)", [])?;
            // Index workdays by date for daily/monthly reporting
            tx.execute("CREATE INDEX IF NOT EXISTS idx_workdays_date ON workdays(date)", [])?;

            Ok(())
        });

        // Version 2: Task templates system for reusable task patterns
        // Introduces the ability to save and reuse common task configurations
        self.add_migration(2, "add_task_templates", |tx| {
            tx.execute(
                "CREATE TABLE IF NOT EXISTS task_templates (
                    id INTEGER PRIMARY KEY,
                    name TEXT NOT NULL UNIQUE,
                    task_name TEXT NOT NULL,
                    comment TEXT,
                    completeness INTEGER DEFAULT 100,
                    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
                )",
                [],
            )?;
            Ok(())
        });

        // Version 3: Tags and categorization system for task organization
        // Adds support for tagging tasks with customizable labels and colors
        self.add_migration(3, "add_tags_system", |tx| {
            // Main tags table for storing tag definitions
            tx.execute(
                "CREATE TABLE IF NOT EXISTS tags (
                    id INTEGER PRIMARY KEY,
                    name TEXT NOT NULL UNIQUE,
                    color TEXT,
                    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
                )",
                [],
            )?;

            // Junction table for many-to-many task-tag relationships
            tx.execute(
                "CREATE TABLE IF NOT EXISTS task_tags (
                    task_id INTEGER NOT NULL,
                    tag_id INTEGER NOT NULL,
                    PRIMARY KEY (task_id, tag_id),
                    FOREIGN KEY (task_id) REFERENCES tasks(id) ON DELETE CASCADE,
                    FOREIGN KEY (tag_id) REFERENCES tags(id) ON DELETE CASCADE
                )",
                [],
            )?;
            Ok(())
        });

        // Version 4: Soft delete functionality for data preservation
        // Enables logical deletion while maintaining data for auditing
        self.add_migration(4, "add_soft_delete", |tx| {
            tx.execute("ALTER TABLE tasks ADD COLUMN deleted_at TIMESTAMP", [])?;
            tx.execute("CREATE INDEX idx_tasks_deleted_at ON tasks(deleted_at)", [])?;
            Ok(())
        });

        // Version 5: Workday notes and annotations for context tracking
        // Allows users to add contextual notes to their workdays
        self.add_migration(5, "add_workday_notes", |tx| {
            tx.execute("ALTER TABLE workdays ADD COLUMN notes TEXT", [])?;
            Ok(())
        });

        // Version 6: Manual breaks table for productivity management
        // Enables users to add manual break periods to improve productivity calculations
        self.add_migration(6, "add_breaks_table", |tx| {
            tx.execute(
                "CREATE TABLE IF NOT EXISTS breaks (
                    id INTEGER PRIMARY KEY,
                    date DATE NOT NULL,
                    start_time DATETIME NOT NULL,
                    end_time DATETIME NOT NULL,
                    duration INTEGER NOT NULL,
                    reason TEXT,
                    created_at DATETIME DEFAULT CURRENT_TIMESTAMP
                )",
                [],
            )?;

            // Create index for efficient daily break lookups
            tx.execute("CREATE INDEX idx_breaks_date ON breaks(date)", [])?;
            Ok(())
        });

        // Version 7: Jira inbox for assigned open issues and toast notifications
        self.add_migration(7, "add_jira_inbox_table", |tx| {
            tx.execute(
                "CREATE TABLE IF NOT EXISTS jira_inbox (
                    issue_key TEXT PRIMARY KEY NOT NULL,
                    issue_id TEXT NOT NULL,
                    summary TEXT NOT NULL,
                    status TEXT NOT NULL,
                    priority TEXT,
                    priority_rank INTEGER NOT NULL DEFAULT 999,
                    url TEXT NOT NULL,
                    first_seen TIMESTAMP NOT NULL,
                    last_seen TIMESTAMP NOT NULL,
                    notified INTEGER NOT NULL DEFAULT 0,
                    pinned INTEGER NOT NULL DEFAULT 0,
                    dismissed INTEGER NOT NULL DEFAULT 0,
                    raw_updated TEXT
                )",
                [],
            )?;
            tx.execute(
                "CREATE INDEX IF NOT EXISTS idx_jira_inbox_active
                 ON jira_inbox(dismissed, pinned DESC, priority_rank ASC, last_seen DESC)",
                [],
            )?;
            Ok(())
        });

        // Version 8: status catalog + scoring/sort_value for inbox ranking
        self.add_migration(8, "jira_inbox_status_id_and_sort_value", |tx| {
            tx.execute(
                "CREATE TABLE IF NOT EXISTS jira_statuses (
                    id TEXT PRIMARY KEY NOT NULL,
                    name TEXT NOT NULL
                )",
                [],
            )?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN status_id TEXT", [])?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN sort_value REAL", [])?;
            tx.execute(
                "CREATE INDEX IF NOT EXISTS idx_jira_inbox_sort
                 ON jira_inbox(dismissed, pinned DESC, sort_value DESC, priority_rank ASC)",
                [],
            )?;
            Ok(())
        });

        // Version 9: wipe legacy status name strings; use status_id + jira_statuses only
        self.add_migration(9, "clear_jira_inbox_legacy_status_text", |tx| {
            tx.execute("UPDATE jira_inbox SET status = ''", [])?;
            Ok(())
        });

        // Version 10: drop unused legacy status text column (canonical: status_id)
        self.add_migration(10, "drop_jira_inbox_legacy_status_column", |tx| {
            tx.execute("ALTER TABLE jira_inbox DROP COLUMN status", [])?;
            Ok(())
        });

        // Version 11: fold manual breaks into pauses as protected records.
        //
        // The separate `breaks` table held synthetic records whose times were
        // invented by a placement heuristic; downstream code converted them to
        // pauses anyway. Manual breaks now live in `pauses` with `protected = 1`,
        // which exempts them from the duration threshold and from merging with
        // adjacent pauses. Existing break rows are carried over so historical
        // reports keep their numbers.
        self.add_migration(11, "fold_breaks_into_protected_pauses", |tx| {
            tx.execute("ALTER TABLE pauses ADD COLUMN protected INTEGER NOT NULL DEFAULT 0", [])?;
            tx.execute("ALTER TABLE pauses ADD COLUMN reason TEXT", [])?;

            // Carry over manual breaks; duration is stored in seconds in `pauses`
            // but was stored in minutes in `breaks`.
            tx.execute(
                "INSERT INTO pauses (start, end, duration, protected, reason)
                 SELECT start_time, end_time, duration * 60, 1, reason FROM breaks",
                [],
            )?;

            tx.execute("DROP INDEX IF EXISTS idx_breaks_date", [])?;
            tx.execute("DROP TABLE IF EXISTS breaks", [])?;
            Ok(())
        });

        // Version 12: inbox reconciliation and change tracking.
        //
        // `gone_at` marks issues that stopped appearing in the Jira poll
        // (closed, reassigned) so the list stops showing them instead of
        // freezing on the first sync. `last_change`/`changed_at` record the
        // most recent visible change (status, priority, score) for badges
        // and toasts.
        self.add_migration(12, "jira_inbox_gone_and_change_tracking", |tx| {
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN gone_at TIMESTAMP", [])?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN last_change TEXT", [])?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN changed_at TIMESTAMP", [])?;
            Ok(())
        });

        // Version 13: the link between an inbox issue and the task it became.
        //
        // `take` used to create a task and dismiss the issue, which severed
        // the two: the key survived only inside the task's name, and the
        // inbox forgot the issue had ever been picked up. `tasks.jira_key`
        // records which issue a task came from, and `jira_inbox.taken_at`
        // keeps the issue in the list marked as taken rather than hiding it.
        //
        // Dismissal stays what it always was - "not my problem" - so rows
        // dismissed before this migration are left alone.
        self.add_migration(13, "link_taken_issues_to_their_tasks", |tx| {
            tx.execute("ALTER TABLE tasks ADD COLUMN jira_key TEXT", [])?;
            tx.execute("CREATE INDEX idx_tasks_jira_key ON tasks(jira_key)", [])?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN taken_at TIMESTAMP", [])?;
            Ok(())
        });

        // Version 14: the outbox of days still owed to kasl-server.
        //
        // A row is a date, not a payload. The day is rebuilt from the local
        // tables when it is finally sent, so a week spent offline delivers the
        // day as it stands at delivery rather than as it stood when the
        // network first failed - the employee's later correction is the one
        // that lands, which is also the rule the server plays by (last upload
        // wins, ADR 0004 in kasl-server).
        //
        // `date` is unique: owing a day twice is the same debt, and a queue
        // that grew a row per failed attempt would send a week's retries as a
        // week's worth of duplicate days.
        //
        // `last_error` and `attempts` are for the person, not the machine.
        // Nothing branches on them; they answer "why is this still here" when
        // a day refuses to leave, which is otherwise invisible.
        self.add_migration(14, "add_server_outbox", |tx| {
            tx.execute(
                "CREATE TABLE IF NOT EXISTS server_outbox (
                    id INTEGER PRIMARY KEY,
                    date DATE NOT NULL UNIQUE,
                    queued_at TIMESTAMP NOT NULL,
                    attempts INTEGER NOT NULL DEFAULT 0,
                    last_attempt_at TIMESTAMP,
                    last_error TEXT
                )",
                [],
            )?;
            // Oldest first is the order the queue is drained in, and the only
            // order it is ever read in.
            tx.execute("CREATE INDEX IF NOT EXISTS idx_server_outbox_date ON server_outbox(date)", [])?;
            Ok(())
        });

        self.add_migration(15, "snooze_inbox_issues", |tx| {
            // Snoozing is "not now", which dismissal could never say: a
            // dismissed issue is gone for good, so the only way to defer one
            // was to leave it in the list and keep reading past it.
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN snoozed_until TIMESTAMP", [])?;
            // When the issue came back, so the return can be announced once
            // and not on every poll after it.
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN woke_at TIMESTAMP", [])?;
            // The waking query asks for rows due before now; the index is what
            // keeps that off a full scan once the inbox is two hundred rows.
            tx.execute("CREATE INDEX IF NOT EXISTS idx_jira_inbox_snoozed ON jira_inbox(snoozed_until)", [])?;
            Ok(())
        });

        // The pulse's last word, kept so `kasl server status` - a different
        // process from the watcher that sends it - can say how it is going.
        //
        // One row, never a log: the server keeps only the latest claim (ADR
        // 0014 in kasl-server), and a local minute-by-minute history of when
        // someone was at their desk would be the record the server refuses
        // to be. `CHECK (id = 1)` makes a second row unwritable rather than
        // merely unwritten.
        //
        // Times are UTC: the only question asked of them is "how long ago",
        // and a wall-clock stamp answers that wrongly for an hour twice a year.
        self.add_migration(16, "add_server_pulse", |tx| {
            tx.execute(
                "CREATE TABLE IF NOT EXISTS server_pulse (
                    id INTEGER PRIMARY KEY CHECK (id = 1),
                    attempted_at TIMESTAMP NOT NULL,
                    next_at TIMESTAMP NOT NULL,
                    sent_at TIMESTAMP,
                    state TEXT,
                    stale_after_seconds INTEGER,
                    clock_skew_seconds INTEGER,
                    error TEXT
                )",
                [],
            )?;
            Ok(())
        });

        // Version 17: why a taken issue left the inbox, and every task its own chain.
        //
        // An issue leaves the inbox when it is resolved or when it stops being
        // yours, and the two ask for opposite things: a resolved issue is a
        // task to mark done, a reassigned one is not. The poll cannot tell them
        // apart - both are simply absent - so kasl asks Jira about each taken
        // issue that left, and keeps the answer. NULL means not asked yet, which
        // is what makes a question that failed get asked again on the next poll.
        // The CHECK keeps a third, unreadable answer out.
        //
        // `task_id = 0` was the default for every task not created through
        // `kasl task add`: issues taken from the inbox, imports from `task find`.
        // The incomplete-task query groups by `task_id`, so all of them were one
        // task to it, and a single finished import hid every unfinished taken
        // issue from `task find`. A task with no history of its own is its own
        // chain; `Tasks::insert` now says so for new rows, and this says it for
        // the old ones.
        self.add_migration(17, "close_the_loop_with_jira", |tx| {
            tx.execute(
                "ALTER TABLE jira_inbox ADD COLUMN left_reason TEXT CHECK (left_reason IN ('resolved', 'moved'))",
                [],
            )?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN resolution TEXT", [])?;
            tx.execute("UPDATE tasks SET task_id = id WHERE task_id = 0", [])?;
            Ok(())
        });

        // Version 18: what inbox rules read, and which rule acted.
        //
        // A rule can say "dismiss every Epic" or "tag work from PAY", so the
        // row has to carry the issue's type and project. Both are the source's
        // own words, kept as text: a Russian Jira calls a bug «Ошибка», and a
        // future GitLab source has projects that are paths, not keys.
        //
        // Existing rows get their project from the key's prefix, which is what
        // a Jira key is; the next poll overwrites it with Jira's own answer.
        // The type is left empty until then - there is nothing to guess it from.
        //
        // `ruled_by` names the rule behind the row's pin or dismissal, so
        // "why is this pinned?" has an answer and an issue a rule hid can be
        // found again. A pin or dismissal by hand clears it.
        //
        // `jira_priorities` is the vocabulary a rule's "High+" is read
        // against: every priority name the inbox has seen, with its rank, and
        // never pruned. Read off the rows of the moment instead, it shrank:
        // the poll that lowered the last High issue made "High" unknown, and
        // a `High+` rule fell asleep in the very poll that raised another
        // issue to Highest. It starts with the names the rows carry now.
        self.add_migration(18, "inbox_rules", |tx| {
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN issue_type TEXT", [])?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN project TEXT", [])?;
            tx.execute("ALTER TABLE jira_inbox ADD COLUMN ruled_by TEXT", [])?;
            tx.execute(
                "UPDATE jira_inbox SET project = substr(issue_key, 1, instr(issue_key, '-') - 1) WHERE instr(issue_key, '-') > 1",
                [],
            )?;
            tx.execute(
                "CREATE TABLE IF NOT EXISTS jira_priorities (
                    name TEXT PRIMARY KEY,
                    rank INTEGER NOT NULL
                )",
                [],
            )?;
            tx.execute(
                "INSERT OR IGNORE INTO jira_priorities (name, rank)
                 SELECT priority, MIN(priority_rank) FROM jira_inbox WHERE priority IS NOT NULL GROUP BY priority",
                [],
            )?;
            Ok(())
        });
    }

    /// Registers a single migration in the migration system.
    ///
    /// This helper method adds a migration to the internal registry with
    /// proper version ordering and validation. It ensures that migrations
    /// are stored in a consistent format for later execution.
    ///
    /// # Panics
    ///
    /// Panics if a migration with the same version number is already registered.
    fn add_migration(&mut self, version: u32, name: &'static str, up: fn(&Transaction) -> Result<()>) {
        self.migrations.push(Migration { version, name, up });
    }

    /// Executes all pending migrations in the correct order.
    ///
    /// # Example
    ///
    /// ```rust
    /// # fn main() -> Result<(), Box<dyn std::error::Error>> {
    /// use kasl::db::migrations::MigrationManager;
    /// use rusqlite::Connection;
    ///
    /// let manager = MigrationManager::new();
    /// let mut conn = Connection::open(":memory:")?;
    /// manager.run_migrations(&mut conn)?;
    /// # Ok(())
    /// # }
    /// ```
    pub fn run_migrations(&self, conn: &mut Connection) -> Result<()> {
        // Initialize the migrations tracking table
        conn.execute(MIGRATIONS_TABLE, [])?;

        // Determine the current schema version
        let current_version = self.get_current_version(conn)?;

        // Find all migrations that haven't been applied yet
        let pending: Vec<&Migration> = self.migrations.iter().filter(|m| m.version > current_version).collect();

        // Exit early if no migrations are needed
        if pending.is_empty() {
            msg_debug!("Database is up to date");
            return Ok(());
        }

        // Notify user about pending migrations
        msg_info!(Message::MigrationsFound(pending.len()));

        // Execute all pending migrations within a single transaction
        let tx = conn.transaction()?;

        for migration in pending {
            msg_info!(Message::RunningMigration(migration.version, migration.name.to_string()));

            match (migration.up)(&tx) {
                Ok(()) => {
                    // Record successful migration in tracking table
                    tx.execute(
                        "INSERT INTO migrations (version, name) VALUES (?1, ?2)",
                        params![migration.version, migration.name],
                    )?;
                    msg_success!(Message::MigrationCompleted(migration.version));
                }
                Err(e) => {
                    // Log migration failure and propagate error
                    msg_error!(Message::MigrationFailed(migration.version, e.to_string()));
                    return Err(e);
                }
            }
        }

        // Commit all successful migrations
        tx.commit()?;
        msg_success!(Message::AllMigrationsCompleted);

        Ok(())
    }

    /// Retrieves the current database schema version.
    fn get_current_version(&self, conn: &Connection) -> Result<u32> {
        let version: Option<u32> = conn.query_row("SELECT MAX(version) FROM migrations", [], |row| row.get(0)).unwrap_or(Some(0));

        Ok(version.unwrap_or(0))
    }

    /// Checks if a specific migration version has been applied.
    ///
    /// This utility method allows callers to verify whether a particular
    /// migration has been successfully applied to the database. Useful
    /// for conditional logic based on schema capabilities.
    ///
    /// # Example
    ///
    /// ```rust
    /// # fn main() -> Result<(), Box<dyn std::error::Error>> {
    /// use kasl::db::migrations::MigrationManager;
    /// use rusqlite::Connection;
    ///
    /// let manager = MigrationManager::new();
    /// let mut conn = Connection::open(":memory:")?;
    /// manager.run_migrations(&mut conn)?;
    /// if manager.is_migration_applied(&conn, 3)? {
    ///     // Tags system is available
    /// }
    /// # Ok(())
    /// # }
    /// ```
    pub fn is_migration_applied(&self, conn: &Connection, version: u32) -> Result<bool> {
        let count: i32 = conn.query_row("SELECT COUNT(*) FROM migrations WHERE version = ?1", params![version], |row| row.get(0))?;

        Ok(count > 0)
    }

    /// Retrieves the complete migration history with timestamps.
    ///
    /// # Example
    ///
    /// ```rust
    /// # fn main() -> Result<(), Box<dyn std::error::Error>> {
    /// use kasl::db::migrations::MigrationManager;
    /// use rusqlite::Connection;
    ///
    /// let manager = MigrationManager::new();
    /// let mut conn = Connection::open(":memory:")?;
    /// manager.run_migrations(&mut conn)?;
    /// let history = manager.get_migration_history(&conn)?;
    /// for (version, name, applied_at) in history {
    ///     println!("v{}: {} ({})", version, name, applied_at);
    /// }
    /// # Ok(())
    /// # }
    /// ```
    pub fn get_migration_history(&self, conn: &Connection) -> Result<Vec<(u32, String, String)>> {
        let mut stmt = conn.prepare("SELECT version, name, applied_at FROM migrations ORDER BY version")?;

        let history = stmt
            .query_map([], |row| Ok((row.get::<_, u32>(0)?, row.get::<_, String>(1)?, row.get::<_, String>(2)?)))?
            .collect::<Result<Vec<_>, _>>()?;

        Ok(history)
    }

    /// Rolls back migrations to a specific target version (debug builds only).
    ///
    /// This development utility allows rolling back migrations to a previous
    /// schema version by removing migration records from the tracking table.
    ///
    /// # Example
    ///
    /// ```rust
    /// # fn main() -> Result<(), Box<dyn std::error::Error>> {
    /// use kasl::db::migrations::MigrationManager;
    /// use rusqlite::Connection;
    ///
    /// #[cfg(debug_assertions)]
    /// {
    ///     let manager = MigrationManager::new();
    ///     let mut conn = Connection::open(":memory:")?;
    ///     manager.run_migrations(&mut conn)?;
    ///     manager.rollback_to(&mut conn, 2)?; // Roll back to version 2
    /// }
    /// # Ok(())
    /// # }
    /// ```
    #[cfg(debug_assertions)]
    pub fn rollback_to(&self, conn: &mut Connection, target_version: u32) -> Result<()> {
        let current_version = self.get_current_version(conn)?;

        if target_version >= current_version {
            msg_info!(Message::NothingToRollback);
            return Ok(());
        }

        msg_info!(Message::RollingBack(current_version, target_version));

        // Remove migration records beyond the target version
        // Note: This is a simplified rollback that doesn't actually reverse schema changes
        conn.execute("DELETE FROM migrations WHERE version > ?1", params![target_version])?;

        msg_success!(Message::RollbackCompleted(target_version));
        Ok(())
    }
}

/// Initializes a database connection with all pending migrations applied.
///
/// This convenience function creates a migration manager and applies all
/// pending migrations to the provided connection. It's the recommended
/// way to ensure a database is up to date with the latest schema.
///
/// # Example
///
/// ```rust,no_run
/// # fn main() -> Result<(), Box<dyn std::error::Error>> {
/// use kasl::db::migrations::init_with_migrations;
/// use rusqlite::Connection;
///
/// let mut conn = Connection::open("kasl.db")?;
/// init_with_migrations(&mut conn)?;
/// # Ok(())
/// # }
/// ```
pub fn init_with_migrations(conn: &mut Connection) -> Result<()> {
    let manager = MigrationManager::new();
    manager.run_migrations(conn)?;
    Ok(())
}

/// Retrieves the current database schema version.
///
/// This utility function provides a simple way to check the current
/// schema version without creating a full migration manager instance.
///
/// # Example
///
/// ```rust
/// # fn main() -> Result<(), Box<dyn std::error::Error>> {
/// use kasl::db::migrations::get_db_version;
/// use rusqlite::Connection;
///
/// let conn = Connection::open(":memory:")?;
/// let version = get_db_version(&conn)?;
/// println!("Current schema version: {}", version);
/// # Ok(())
/// # }
/// ```
pub fn get_db_version(conn: &Connection) -> Result<u32> {
    let manager = MigrationManager::new();
    manager.get_current_version(conn)
}

/// Checks if the database requires migration to the latest schema version.
///
/// This utility function compares the current database version with the
/// latest available migration version to determine if updates are needed.
///
/// # Example
///
/// ```rust
/// # fn main() -> Result<(), Box<dyn std::error::Error>> {
/// use kasl::db::migrations::needs_migration;
/// use rusqlite::Connection;
///
/// let conn = Connection::open(":memory:")?;
/// if needs_migration(&conn)? {
///     println!("Database needs migration!");
/// }
/// # Ok(())
/// # }
/// ```
pub fn needs_migration(conn: &Connection) -> Result<bool> {
    let manager = MigrationManager::new();
    let current = manager.get_current_version(conn)?;
    let latest = manager.migrations.last().map(|m| m.version).unwrap_or(0);
    Ok(current < latest)
}