fix: Fix PostgreSQL migration SQL parsing with dollar-quoted strings

This release fixes critical bugs in the PostgreSQL migration runner that were
causing "unterminated dollar-quoted string" errors when executing migrations
containing PL/pgSQL functions with dollar-quoted string literals.

## Key Fixes

### Enhanced SQL Parsing Logic
- Fixed `split_sql_respecting_quotes` function to properly handle empty dollar tags (`$$...$$`)
- Improved comment filtering to distinguish SQL statements from comment-only blocks
- Enhanced parsing of complex nested structures in dollar-quoted contexts

### Migration 014 Fix
- Resolved "unterminated dollar-quoted string" error in migration 014
- Fixed parsing of PL/pgSQL function definitions with dollar-quoted bodies
- Ensured proper trigger and function creation statements are executed correctly

### Comprehensive Test Coverage
- Added `test_migration_012_sql_parsing` to validate complex transaction parsing
- Added `test_migration_014_sql_parsing` to validate dollar-quoted function parsing
- Added `test_dollar_quoted_string_parsing` for general dollar-quote validation
- Ensured `sqlparser-rs` integration works correctly with PostgreSQL features

## Validation
- All 22 statements in migration 012 now parse correctly
- All 5 statements in migration 014 now parse correctly including PL/pgSQL functions
- Complex SQL features validated: CASE expressions, subqueries, UUID arrays, constraints

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: CodingAnarchy

CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.15.2] - 2025-01-25
+
+### Fixed
+- **🔧 SQL Migration Parsing Improvements**
+  - Fixed critical bug in PostgreSQL migration runner where dollar-quoted strings (`$$...$$`) were not properly parsed
+  - Enhanced `split_sql_respecting_quotes` function to correctly handle empty dollar tags and complex nested structures
+  - Improved comment filtering logic to properly distinguish between comment-only blocks and executable SQL statements
+  - Fixed migration 014 execution which was failing with "unterminated dollar-quoted string" errors
+  - Added comprehensive test coverage for both migration 012 and 014 SQL parsing validation
+  - Validated complex SQL structures including PL/pgSQL functions, multi-line CASE expressions, and transaction blocks
+  - Ensured `sqlparser-rs` integration works correctly with PostgreSQL-specific syntax features
+
 ## [1.15.1] - 2025-01-23
 
 ### Added

Cargo.toml

@@ -9,7 +9,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "1.15.1"
+version = "1.15.2"
 edition = "2024"
 license = "MIT"
 repository = "https://github.com/CodingAnarchy/hammerwork"

hammerwork-web/src/api/archive.rs

@@ -406,11 +406,7 @@ where
                 // If we got exactly the limit, there might be more records
                 // Run another query to get a better count estimate
                 match queue
-                    .list_archived_jobs(
-                        filters.queue.as_deref(),
-                        Some(10000),
-                        Some(0),
-                    )
+                    .list_archived_jobs(filters.queue.as_deref(), Some(10000), Some(0))
                     .await
                 {
                     Ok(all_jobs) => all_jobs.len() as u64,
@@ -481,10 +477,7 @@ where
     if request.dry_run {
         // For dry run, estimate how many jobs would be purged by using list_archived_jobs
         // with a large limit to get an accurate count
-        let count = match queue
-            .list_archived_jobs(None, Some(10000), Some(0))
-            .await
-        {
+        let count = match queue.list_archived_jobs(None, Some(10000), Some(0)).await {
             Ok(jobs) => jobs.len() as u64,
             Err(_) => 0, // If we can't get the count, return 0 for safety
         };

src/migrations/mysql.rs

@@ -8,7 +8,9 @@ use sqlx::{MySqlPool, Row};
 use tracing::{debug, info, warn};
 
 /// Parse SQL text into individual statements using sqlparser-rs for MySQL
-fn parse_mysql_statements(sql: &str) -> std::result::Result<Vec<String>, sqlparser::parser::ParserError> {
+fn parse_mysql_statements(
+    sql: &str,
+) -> std::result::Result<Vec<String>, sqlparser::parser::ParserError> {
     let dialect = MySqlDialect {};
 
     match Parser::parse_sql(&dialect, sql) {