execsql2 2.22.5__tar.gz → 2.22.7__tar.gz

{execsql2-2.22.5 → execsql2-2.22.7}/.github/workflows/ci-cd.yml

@@ -21,7 +21,7 @@ jobs:
             contents: read
         steps:
             - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
-            - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+            - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: "3.13"
             - run: python -m pip install ruff
@@ -35,7 +35,7 @@ jobs:
             contents: read
         steps:
             - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
-            - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+            - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: "3.13"
                   cache: "pip"
@@ -50,7 +50,7 @@ jobs:
             contents: read
         steps:
             - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
-            - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+            - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: "3.13"
                   cache: "pip"
@@ -68,7 +68,7 @@ jobs:
             contents: read
         steps:
             - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
-            - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+            - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: "3.13"
                   cache: "pip"
@@ -99,7 +99,7 @@ jobs:
             - name: Check out repository code
               uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
             - name: Setup Python ${{ matrix.python-version }}
-              uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+              uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: ${{ matrix.python-version }}
             - name: Cache pip dependencies
@@ -190,7 +190,7 @@ jobs:
             - name: Check out repository code
               uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
             - name: Setup Python ${{ matrix.python-version }}
-              uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+              uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: ${{ matrix.python-version }}
             - name: Install tkinter (Ubuntu)
@@ -237,7 +237,7 @@ jobs:
             contents: read
         steps:
             - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
-            - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+            - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: ${{ matrix.python-version }}
             - name: Install Microsoft Access Database Engine 2016 (x64)
@@ -290,7 +290,7 @@ jobs:
         steps:
             - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0  # v7.0.0
             - name: Set up Python
-              uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1  # v6.3.0
+              uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
               with:
                   python-version: "3.13"
                   cache: "pip"

{execsql2-2.22.5 → execsql2-2.22.7}/CHANGELOG.md

@@ -13,6 +13,29 @@ ______________________________________________________________________
 
 ______________________________________________________________________
 
+## [2.22.7] - 2026-09-17
+
+### Fixed
+
+- `execsql-format` no longer deletes clauses from SQL it cannot fully parse. `INSERT ... CROSS JOIN LATERAL (VALUES ...) AS g(a, b) ON CONFLICT (a) DO NOTHING` was rewritten without its `DO NOTHING`, and `--in-place` reported the result as `reformatted`.
+- `execsql-format` no longer deletes a substitution variable that supplies a conditional clause. A `!!~var!!` standing alone in a `WHERE` clause — the pattern the shipped upsert templates use for optional predicates — was dropped from the formatted output, as was a trailing `ORDER BY` in the same statement.
+
+### Changed
+
+- `execsql-format` leaves a run of SQL untouched when any statement in it fails to parse, instead of reformatting from a partial parse. Affected statements keep their original layout; only their indentation is normalized.
+
+______________________________________________________________________
+
+## [2.22.6] - 2026-08-28
+
+### Fixed
+
+- `execsql-format` no longer indents inside a multi-line string literal. A `$$…$$` body or a multi-line `'…'` string inside an `IF`, `LOOP`, or `BEGIN SQL` block had the block's indentation added to each of its lines, changing the value the database stores.
+- `execsql-format --leading-comma` no longer moves a comma into or out of a multi-line string literal, which rewrote the stored value.
+- `execsql-format` now reaches a stable result in one pass. A statement sqlglot could not parse gained a space of indentation on every run and never converged, so `--check` could not pass on an already-formatted file; two adjacent comments on one statement also cost an extra pass.
+
+______________________________________________________________________
+
 ## [2.22.5] - 2026-08-27
 
 ### Fixed

{execsql2-2.22.5 → execsql2-2.22.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: execsql2
-Version: 2.22.5
+Version: 2.22.7
 Summary: Runs a SQL script against a PostgreSQL, SQLite, MariaDB/MySQL, DuckDB, Firebird, MS-Access, MS-SQL-Server, or Oracle database, or an ODBC DSN. Provides metacommands to import and export data, copy data between databases, conditionally execute SQL and metacommands, and dynamically alter SQL and metacommands with substitution variables.
 Project-URL: Homepage, https://execsql2.readthedocs.io
 Project-URL: Repository, https://github.com/geocoug/execsql
@@ -384,7 +384,7 @@ execsql-format --no-sql --in-place scripts/
 ```yaml
 repos:
   - repo: https://github.com/geocoug/execsql
-    rev: v2.22.5
+    rev: v2.22.7
     hooks:
       - id: execsql-format
 ```

{execsql2-2.22.5 → execsql2-2.22.7}/README.md

@@ -253,7 +253,7 @@ execsql-format --no-sql --in-place scripts/
 ```yaml
 repos:
   - repo: https://github.com/geocoug/execsql
-    rev: v2.22.5
+    rev: v2.22.7
     hooks:
       - id: execsql-format
 ```

{execsql2-2.22.5 → execsql2-2.22.7}/docs/about/divergence.md

@@ -272,53 +272,57 @@ These are behavioral changes driven by security or correctness issues in the ups
 
 ### Bug Fixes
 
-| Area                                                  | Fix                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Oracle default port                                   | Corrected from `5432` (PostgreSQL) to `1521`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| MySQL `LOAD DATA INFILE` encoding                     | Python encoding names are now mapped to MySQL charset names.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `dt_cast` type converters                             | Base `Database` class auto-populates 8 type converters that were previously left empty after the refactor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| `FileWriter` CPU busy-loop                            | Uses blocking `queue.get(timeout=0.1)` instead of `get_nowait()` in a tight loop.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| Substitution variable cycles                          | 100-iteration limit prevents infinite loops on cyclic variable references.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| Script location in error messages                     | `ErrInfo.script_file` and `script_line_no` are now populated via `stamp_errinfo()` so error output includes "Line N of script foo.sql" context — restoring behavior present in the monolith.                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `$ERROR_MESSAGE` not updated                          | `$ERROR_MESSAGE` is now set on every error path: `exit_now()`, non-halting SQL errors, and non-halting metacommand errors. Previously it was initialized to `""` and never changed.                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| Metacommand error message lost                        | When `halt_on_metacommand_err` is `ON`, the original handler `ErrInfo` is now re-raised; the generic "Unknown metacommand" message no longer replaces the specific error from the handler.                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| Empty script name in error msg                        | `_execute_script_direct()` and `_execute_script_textual_console()` no longer append "in script , line 0" to uncaught-exception messages when `current_script_line()` returns an empty string.                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| `PROMPT COMPARE` diff comparison                      | Diff engine uses native Python equality instead of string comparison — numeric types, Decimals, and booleans compare correctly. `None` is distinguished from empty string. Columns are matched by name (not position), key columns are excluded from comparison, and duplicate PKs keep the first row.                                                                                                                                                                                                                                                                                                         |
-| `win_config_file` broken                              | Checked `os.name == "windows"` which Python never returns (correct value is `"nt"`). Fixed to `os.name == "nt"`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ELSEIF + ANDIF/ORIF                                   | ANDIF/ORIF after an ELSEIF were silently attached to the parent IF condition instead of the ELSEIF clause. The compound condition was never evaluated for the ELSEIF branch. Fixed in the AST parser and executor.                                                                                                                                                                                                                                                                                                                                                                                             |
-| Cursor leak in `select_rowsource()`                   | Cursor was not closed on query execution failure. Row generators in EXPORT and COPY paths were not explicitly closed on error, relying on garbage collection for cleanup.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| `NumericParser` right-associative                     | Arithmetic operators were parsed right-to-left. `10 - 3 - 2` evaluated as `9` instead of `5`. Fixed to left-associative parsing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| Empty-column check precedence                         | `DataTable` and `Database.populate_table()` had an operator precedence bug in the extra-column emptiness check — a redundant `and conf.del_empty_cols` caused incorrect short-circuit evaluation.                                                                                                                                                                                                                                                                                                                                                                                                              |
-| SQLite import string processing                       | `SQLiteDatabase.populate_table()` applied `trim_strings`, `replace_newlines`, and `empty_strings` after copying row data, so processing never reached the INSERT. Fixed to process before extraction.                                                                                                                                                                                                                                                                                                                                                                                                          |
-| `$CURRENT_DATABASE`/`$CURRENT_DBMS` stale after USE   | These variables were only set at startup and on CONNECT, not refreshed when `USE` switched the active database. Now set in `set_static_system_vars()` so they update on any connection change.                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `DT_Text.data_type_name` wrong                        | Was `"character"` (same as `DT_Character`), making error messages indistinguishable. Corrected to `"text"`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| `DT_Varchar` non-string data unchecked                | `_from_data()` only enforced the 255-char limit for `str` inputs; non-string values passed through without conversion or length check.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `WriteHooks.write_err()` crash on empty string        | `strval[-1]` raised `IndexError` on empty input. Fixed to use `str.endswith()`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| `NumericParser` division by zero                      | `NumericAstNode.eval()` raised unhandled `ZeroDivisionError`. Now raises `NumericParserError` with a clear message.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `CondAstNode.eval()` could return `None`              | Missing fallthrough for unknown node types silently returned `None`. Now raises `CondParserError`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `DT_Timestamp` claims time-only values                | `dateutil.parser.parse()` silently fills in today's date for bare time strings like `"13:15:45"`, so `DT_Timestamp` matched before `DT_Time` in the inference order. `parse_datetime()` now rejects time-only strings.                                                                                                                                                                                                                                                                                                                                                                                         |
-| `CounterVars.substitute` skipped pos 0–1              | `re.I` was passed as the positional `pos` argument, skipping the first 2 characters of every string during counter variable expansion. Counter variables at the very start of a line were never matched.                                                                                                                                                                                                                                                                                                                                                                                                       |
-| `exec_cmd` (SQLite/DuckDB) always raised TypeError    | Passed bytes to `curs.execute()` via `.encode()`, which Python 3 `sqlite3`/`duckdb` reject. `EXECUTE PROCEDURE` metacommand was non-functional on these backends.                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| MySQL `LOAD DATA INFILE` injection                    | File path, delimiter, and quotechar were interpolated without escaping. Now single-quotes are escaped consistent with the PostgreSQL COPY path.                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| Missing server/database name at connect               | Connecting to a server-based database without a server or database name now stops with a clear fatal error ("Configured database requires a server name, but none is provided.") instead of crashing inside the driver with a `TypeError`.                                                                                                                                                                                                                                                                                                                                                                     |
-| Config file chain infinite loop                       | The `config_file` directive could chain config files without limit. A circular reference (via symlinks or different relative paths) caused an infinite loop at startup. Now capped at 20 files.                                                                                                                                                                                                                                                                                                                                                                                                                |
-| Cursor leaks in database adapters                     | ~15 methods across all adapters used `curs = self.cursor()` / `curs.close()` without `try/finally`. If the query raised, the cursor leaked. Converted to `with self._cursor() as curs:`.                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| JSON export malformed on special column names         | Column names containing `"` or `\` produced invalid JSON. Now uses `json.dumps()` for all field names.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| Temp file creation TOCTOU race                        | `TempFileMgr.new_temp_fn()` discarded the `NamedTemporaryFile` handle, creating a race window. Now uses `tempfile.mkstemp()` for secure creation.                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `shlex.split` on Windows incorrect mode               | Called without `posix=False` on Windows, mishandling backslash-heavy paths in SHELL commands.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| AST executor `~`/`+` variable scoping broken          | The AST executor passed `localvars` through function parameters but never pushed `CommandList` frames onto `commandliststack`. Legacy metacommand handlers (`x_sub`, `x_rm_sub`, `xf_sub_defined`, `SUB_LOCAL`, prompt handlers, REPL) access `commandliststack[-1]` for `~` local and `+` outer-scope variables. This caused `~` vars to be invisible to SQL, `SUB_DEFINED(~var)` to always return false, and the REPL `.vars`/`.stack` to show empty state. Fixed by pushing/popping `CommandList` frames in `execute()` and `_execute_script_native()`.                                                     |
-| Firebird adapter import                               | Adapter imported `fdb` (the unmaintained legacy driver) while the `[firebird]` extra declared `firebird-driver`. `pip install execsql2[firebird]` followed by a Firebird connect raised `ModuleNotFoundError: No module named 'fdb'`. Adapter now imports `firebird.driver`, matching the declared dependency.                                                                                                                                                                                                                                                                                                 |
-| Connect timeouts on network adapters                  | MySQL, SQL Server / Access / DSN (pyodbc), Firebird, and SMTP all now apply a 30 s connect timeout matching the existing PostgreSQL default. A silently-dropped network peer (firewall rule, dead VM) used to hang scripts indefinitely; now the connect fails fast.                                                                                                                                                                                                                                                                                                                                           |
-| AST parser INCLUDE quoted paths broken                | The AST parser captured the full INCLUDE target including surrounding quotes (`"path"`), but the legacy dispatch regex stripped them. Quoted INCLUDE paths failed with "File does not exist" even when the file was present. Fixed by stripping matched quote pairs in the parser.                                                                                                                                                                                                                                                                                                                             |
-| AST parser `BEGIN SCRIPT name(params)` rejected       | The regex required whitespace between the script name and parameter list. `BEGIN SCRIPT foo(a,b)` (no space before `(`) silently failed to match, causing the matching `END SCRIPT` to raise "Unmatched END SCRIPT metacommand." Fixed by allowing optional whitespace before the parameter expression.                                                                                                                                                                                                                                                                                                        |
-| AST executor forward SCRIPT references broken         | The legacy engine registered all `BEGIN SCRIPT` blocks at parse time (two-pass), so `EXECUTE SCRIPT foo` could appear before the `BEGIN SCRIPT foo` definition. The AST executor walked the tree in a single pass, so forward references failed with "There is no SCRIPT named foo." Fixed by adding a pre-registration scan of all SCRIPT blocks before execution begins.                                                                                                                                                                                                                                     |
-| DB-export type inference overrides source types       | `DataTable`/`Column` inferred column types from the *string shape* of values — correct for CSV import (everything is `str`) but wrong for DB-query exports where the driver returns typed Python objects. A text column with values like `"2026-06-30 10:07:20 PM"` was inferred as `TIMESTAMP`, causing DuckDB bind errors. SQLite, DuckDB, HDF5, and JSON-schema exports now pass `infer_strings=False` to `DataTable`: string values are classified as text types only, while native Python objects (`Decimal`, `datetime`, etc.) still run through the full accumulator set for accurate schema inference. |
-| `EXPORT FORMAT SQLITE` rejects `decimal.Decimal`      | SQLite's Python adapter does not accept `Decimal` in `executemany`, raising `ProgrammingError`. SQLite exports now convert `Decimal` values to their exact string representation before binding; SQLite's NUMERIC affinity stores them without loss of precision.                                                                                                                                                                                                                                                                                                                                              |
-| Unsupported Python objects crash native exports       | `EXPORT FORMAT SQLITE` and `EXPORT FORMAT DUCKDB` raised bind errors when the DB driver returned user-defined Python objects (e.g. PostGIS geometry). Both exporters now stringify any object whose type is not in the adapter's safe-binding set, preserving values as their `str()` form instead of crashing.                                                                                                                                                                                                                                                                                                |
-| `HALT` with a message hangs unattended runs           | The message-bearing `HALT` patterns are registered after the general one and so take priority, meaning `x_halt`'s `gui_level > 1` guard was never reached and every `HALT MESSAGE` opened a modal dialog — blocking cron and CI runs indefinitely at `gui_level` 0, contrary to the documented behavior. The guard now lives in `x_halt_msg`: without a GUI console and below `gui_level` 2, the message and any `DISPLAY` rowset are written to the error output and the script exits with the requested status. An empty `DISPLAY` table renders as headings plus a zero row count rather than nothing.      |
-| Textual `HALT` dialog ignored `button_list`           | The Textual `MsgScreen` hardcoded a Cancel/Continue pair and dropped the caller's `column_headers`/`rowset`, so a `HALT` asking for a single OK button offered a Cancel that exited with status 2 instead of the requested `EXIT_STATUS`, and `HALT ... DISPLAY` showed no table. `MsgScreen` now honors `button_list` and `no_cancel` (which also suppresses <kbd>Esc</kbd>) and renders the rowset, matching the Tkinter backend.                                                                                                                                                                            |
-| `execsql-format` corrupts `E'...'` literals           | sqlglot's Postgres tokenizer consumes backslash escapes inside an escape string but its generator never re-emits them (tobymao/sqlglot#8191), so `E'\\s+'` became `e'\s+'` — a regex matching the letter `s` rather than whitespace — losing one backslash per pass until `E'\\\\'` degraded to the unparsable `e'\''`. Escape strings are now masked out of the sqlglot round trip and restored byte-for-byte, independently of the installed sqlglot version.                                                                                                                                                |
-| Formatter could not detect literal-level content loss | The content-loss guard deleted every non-alphanumeric character before comparing *lengths*, so any rewrite confined to punctuation was invisible to it at any threshold. A literal round-trip check now requires every string literal in the input to survive verbatim in the output, falling back to the unformatted text otherwise.                                                                                                                                                                                                                                                                          |
+| Area                                                  | Fix                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Oracle default port                                   | Corrected from `5432` (PostgreSQL) to `1521`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| MySQL `LOAD DATA INFILE` encoding                     | Python encoding names are now mapped to MySQL charset names.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `dt_cast` type converters                             | Base `Database` class auto-populates 8 type converters that were previously left empty after the refactor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `FileWriter` CPU busy-loop                            | Uses blocking `queue.get(timeout=0.1)` instead of `get_nowait()` in a tight loop.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Substitution variable cycles                          | 100-iteration limit prevents infinite loops on cyclic variable references.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Script location in error messages                     | `ErrInfo.script_file` and `script_line_no` are now populated via `stamp_errinfo()` so error output includes "Line N of script foo.sql" context — restoring behavior present in the monolith.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `$ERROR_MESSAGE` not updated                          | `$ERROR_MESSAGE` is now set on every error path: `exit_now()`, non-halting SQL errors, and non-halting metacommand errors. Previously it was initialized to `""` and never changed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Metacommand error message lost                        | When `halt_on_metacommand_err` is `ON`, the original handler `ErrInfo` is now re-raised; the generic "Unknown metacommand" message no longer replaces the specific error from the handler.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Empty script name in error msg                        | `_execute_script_direct()` and `_execute_script_textual_console()` no longer append "in script , line 0" to uncaught-exception messages when `current_script_line()` returns an empty string.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `PROMPT COMPARE` diff comparison                      | Diff engine uses native Python equality instead of string comparison — numeric types, Decimals, and booleans compare correctly. `None` is distinguished from empty string. Columns are matched by name (not position), key columns are excluded from comparison, and duplicate PKs keep the first row.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `win_config_file` broken                              | Checked `os.name == "windows"` which Python never returns (correct value is `"nt"`). Fixed to `os.name == "nt"`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ELSEIF + ANDIF/ORIF                                   | ANDIF/ORIF after an ELSEIF were silently attached to the parent IF condition instead of the ELSEIF clause. The compound condition was never evaluated for the ELSEIF branch. Fixed in the AST parser and executor.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Cursor leak in `select_rowsource()`                   | Cursor was not closed on query execution failure. Row generators in EXPORT and COPY paths were not explicitly closed on error, relying on garbage collection for cleanup.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `NumericParser` right-associative                     | Arithmetic operators were parsed right-to-left. `10 - 3 - 2` evaluated as `9` instead of `5`. Fixed to left-associative parsing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Empty-column check precedence                         | `DataTable` and `Database.populate_table()` had an operator precedence bug in the extra-column emptiness check — a redundant `and conf.del_empty_cols` caused incorrect short-circuit evaluation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| SQLite import string processing                       | `SQLiteDatabase.populate_table()` applied `trim_strings`, `replace_newlines`, and `empty_strings` after copying row data, so processing never reached the INSERT. Fixed to process before extraction.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `$CURRENT_DATABASE`/`$CURRENT_DBMS` stale after USE   | These variables were only set at startup and on CONNECT, not refreshed when `USE` switched the active database. Now set in `set_static_system_vars()` so they update on any connection change.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `DT_Text.data_type_name` wrong                        | Was `"character"` (same as `DT_Character`), making error messages indistinguishable. Corrected to `"text"`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `DT_Varchar` non-string data unchecked                | `_from_data()` only enforced the 255-char limit for `str` inputs; non-string values passed through without conversion or length check.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `WriteHooks.write_err()` crash on empty string        | `strval[-1]` raised `IndexError` on empty input. Fixed to use `str.endswith()`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `NumericParser` division by zero                      | `NumericAstNode.eval()` raised unhandled `ZeroDivisionError`. Now raises `NumericParserError` with a clear message.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `CondAstNode.eval()` could return `None`              | Missing fallthrough for unknown node types silently returned `None`. Now raises `CondParserError`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `DT_Timestamp` claims time-only values                | `dateutil.parser.parse()` silently fills in today's date for bare time strings like `"13:15:45"`, so `DT_Timestamp` matched before `DT_Time` in the inference order. `parse_datetime()` now rejects time-only strings.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| `CounterVars.substitute` skipped pos 0–1              | `re.I` was passed as the positional `pos` argument, skipping the first 2 characters of every string during counter variable expansion. Counter variables at the very start of a line were never matched.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `exec_cmd` (SQLite/DuckDB) always raised TypeError    | Passed bytes to `curs.execute()` via `.encode()`, which Python 3 `sqlite3`/`duckdb` reject. `EXECUTE PROCEDURE` metacommand was non-functional on these backends.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| MySQL `LOAD DATA INFILE` injection                    | File path, delimiter, and quotechar were interpolated without escaping. Now single-quotes are escaped consistent with the PostgreSQL COPY path.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Missing server/database name at connect               | Connecting to a server-based database without a server or database name now stops with a clear fatal error ("Configured database requires a server name, but none is provided.") instead of crashing inside the driver with a `TypeError`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Config file chain infinite loop                       | The `config_file` directive could chain config files without limit. A circular reference (via symlinks or different relative paths) caused an infinite loop at startup. Now capped at 20 files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| Cursor leaks in database adapters                     | ~15 methods across all adapters used `curs = self.cursor()` / `curs.close()` without `try/finally`. If the query raised, the cursor leaked. Converted to `with self._cursor() as curs:`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| JSON export malformed on special column names         | Column names containing `"` or `\` produced invalid JSON. Now uses `json.dumps()` for all field names.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Temp file creation TOCTOU race                        | `TempFileMgr.new_temp_fn()` discarded the `NamedTemporaryFile` handle, creating a race window. Now uses `tempfile.mkstemp()` for secure creation.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `shlex.split` on Windows incorrect mode               | Called without `posix=False` on Windows, mishandling backslash-heavy paths in SHELL commands.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| AST executor `~`/`+` variable scoping broken          | The AST executor passed `localvars` through function parameters but never pushed `CommandList` frames onto `commandliststack`. Legacy metacommand handlers (`x_sub`, `x_rm_sub`, `xf_sub_defined`, `SUB_LOCAL`, prompt handlers, REPL) access `commandliststack[-1]` for `~` local and `+` outer-scope variables. This caused `~` vars to be invisible to SQL, `SUB_DEFINED(~var)` to always return false, and the REPL `.vars`/`.stack` to show empty state. Fixed by pushing/popping `CommandList` frames in `execute()` and `_execute_script_native()`.                                                                                                                                                                                                                                                         |
+| Firebird adapter import                               | Adapter imported `fdb` (the unmaintained legacy driver) while the `[firebird]` extra declared `firebird-driver`. `pip install execsql2[firebird]` followed by a Firebird connect raised `ModuleNotFoundError: No module named 'fdb'`. Adapter now imports `firebird.driver`, matching the declared dependency.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| Connect timeouts on network adapters                  | MySQL, SQL Server / Access / DSN (pyodbc), Firebird, and SMTP all now apply a 30 s connect timeout matching the existing PostgreSQL default. A silently-dropped network peer (firewall rule, dead VM) used to hang scripts indefinitely; now the connect fails fast.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| AST parser INCLUDE quoted paths broken                | The AST parser captured the full INCLUDE target including surrounding quotes (`"path"`), but the legacy dispatch regex stripped them. Quoted INCLUDE paths failed with "File does not exist" even when the file was present. Fixed by stripping matched quote pairs in the parser.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| AST parser `BEGIN SCRIPT name(params)` rejected       | The regex required whitespace between the script name and parameter list. `BEGIN SCRIPT foo(a,b)` (no space before `(`) silently failed to match, causing the matching `END SCRIPT` to raise "Unmatched END SCRIPT metacommand." Fixed by allowing optional whitespace before the parameter expression.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| AST executor forward SCRIPT references broken         | The legacy engine registered all `BEGIN SCRIPT` blocks at parse time (two-pass), so `EXECUTE SCRIPT foo` could appear before the `BEGIN SCRIPT foo` definition. The AST executor walked the tree in a single pass, so forward references failed with "There is no SCRIPT named foo." Fixed by adding a pre-registration scan of all SCRIPT blocks before execution begins.                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| DB-export type inference overrides source types       | `DataTable`/`Column` inferred column types from the *string shape* of values — correct for CSV import (everything is `str`) but wrong for DB-query exports where the driver returns typed Python objects. A text column with values like `"2026-06-30 10:07:20 PM"` was inferred as `TIMESTAMP`, causing DuckDB bind errors. SQLite, DuckDB, HDF5, and JSON-schema exports now pass `infer_strings=False` to `DataTable`: string values are classified as text types only, while native Python objects (`Decimal`, `datetime`, etc.) still run through the full accumulator set for accurate schema inference.                                                                                                                                                                                                     |
+| `EXPORT FORMAT SQLITE` rejects `decimal.Decimal`      | SQLite's Python adapter does not accept `Decimal` in `executemany`, raising `ProgrammingError`. SQLite exports now convert `Decimal` values to their exact string representation before binding; SQLite's NUMERIC affinity stores them without loss of precision.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Unsupported Python objects crash native exports       | `EXPORT FORMAT SQLITE` and `EXPORT FORMAT DUCKDB` raised bind errors when the DB driver returned user-defined Python objects (e.g. PostGIS geometry). Both exporters now stringify any object whose type is not in the adapter's safe-binding set, preserving values as their `str()` form instead of crashing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `HALT` with a message hangs unattended runs           | The message-bearing `HALT` patterns are registered after the general one and so take priority, meaning `x_halt`'s `gui_level > 1` guard was never reached and every `HALT MESSAGE` opened a modal dialog — blocking cron and CI runs indefinitely at `gui_level` 0, contrary to the documented behavior. The guard now lives in `x_halt_msg`: without a GUI console and below `gui_level` 2, the message and any `DISPLAY` rowset are written to the error output and the script exits with the requested status. An empty `DISPLAY` table renders as headings plus a zero row count rather than nothing.                                                                                                                                                                                                          |
+| Textual `HALT` dialog ignored `button_list`           | The Textual `MsgScreen` hardcoded a Cancel/Continue pair and dropped the caller's `column_headers`/`rowset`, so a `HALT` asking for a single OK button offered a Cancel that exited with status 2 instead of the requested `EXIT_STATUS`, and `HALT ... DISPLAY` showed no table. `MsgScreen` now honors `button_list` and `no_cancel` (which also suppresses <kbd>Esc</kbd>) and renders the rowset, matching the Tkinter backend.                                                                                                                                                                                                                                                                                                                                                                                |
+| `execsql-format` corrupts `E'...'` literals           | sqlglot's Postgres tokenizer consumes backslash escapes inside an escape string but its generator never re-emits them (tobymao/sqlglot#8191), so `E'\\s+'` became `e'\s+'` — a regex matching the letter `s` rather than whitespace — losing one backslash per pass until `E'\\\\'` degraded to the unparsable `e'\''`. Escape strings are now masked out of the sqlglot round trip and restored byte-for-byte, independently of the installed sqlglot version.                                                                                                                                                                                                                                                                                                                                                    |
+| Formatter could not detect literal-level content loss | The content-loss guard deleted every non-alphanumeric character before comparing *lengths*, so any rewrite confined to punctuation was invisible to it at any threshold. A literal round-trip check now requires every string literal in the input to survive verbatim in the output, falling back to the unformatted text otherwise.                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Formatter indents inside multi-line literals          | Block indentation was applied to every line of a multi-line literal (`$$…$$` body or a `'…'` string spanning lines), so a literal inside an `IF`, `LOOP`, or `BEGIN SQL` block gained the block's leading whitespace on each continuation line — changing the value stored by the database. Lines that begin inside a dollar-quoted literal are now emitted verbatim and excluded from the indent arithmetic. Neither the literal round-trip guard (which covers only the sqlglot round trip) nor the existing idempotency test (which compares pass 1 to pass 2, while the indent is applied once and then stable) could detect it.                                                                                                                                                                               |
+| Comma passes rewrite multi-line literals              | `--leading-comma` and the trailing-comma normalization that precedes it moved a comma across a line break inside a multi-line literal, changing the stored value. Both now skip every line such a literal touches.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Formatter never converged on unparsable statements    | Comments are hidden from sqlglot as `/* marker */ line`. Removing the marker left the injected separator space behind, which was then measured as indentation — so a statement sqlglot could not parse (and therefore returned verbatim) gained one space on every run and never reached a fixed point, leaving `--check` permanently failing. Adjacent comments compounded it, leaving residue mid-expression that took a second pass to normalise. Marker runs are now removed together with the whitespace they introduced, and indentation is read from the line itself.                                                                                                                                                                                                                                       |
+| Formatter dropped clauses from unparsable SQL         | The sqlglot parse ran at `ErrorLevel.IGNORE`, which answers a statement it cannot parse with a partial AST rather than an error — the tokens it failed on are absent, and regenerating from that AST wrote back SQL the author never had. `INSERT ... CROSS JOIN LATERAL (VALUES ...) AS g(a, b) ON CONFLICT (a) DO NOTHING` came back without its `DO NOTHING`, a syntax error that `--in-place` reported as `reformatted`. Every guard passed it: one statement for one semicolon, 88% of the input's alphanumeric characters, and no string literals to round-trip. The guards are quantitative and the loss is qualitative — a dropped `DISTINCT`, `CASCADE`, `DESC`, or `NOT` is smaller still — so the parse now runs at `ErrorLevel.RAISE` and SQL that does not fully parse is emitted exactly as written. |
 
 ______________________________________________________________________
 

{execsql2-2.22.5 → execsql2-2.22.7}/docs/guides/formatter.md

@@ -89,20 +89,35 @@ Block comments (`/* */`) that contain `-- !x!` metacommand markers (e.g. comment
 
 #### Variable preservation
 
-execsql substitution variables (`!!varname!!`, `!{varname}!`) are replaced with valid SQL identifiers before formatting, then restored afterward, so the formatter does not corrupt them — including in schema-qualified names (`!!staging!!.!!table!!`), CASE expressions, JOIN conditions, and string concatenation.
+execsql substitution variables (`!!varname!!`, `!{varname}!`) are replaced with valid SQL identifiers before formatting, then restored afterward, so the formatter does not corrupt them — including in schema-qualified names (`!!staging!!.!!table!!`), CASE expressions, JOIN conditions, and string concatenation. A variable that holds a *fragment* rather than a value — a `!!~var!!` standing alone in a `WHERE` clause, as the upsert templates use for optional predicates — leaves the statement unparsable once masked, so the statement is passed through untouched rather than reformatted without it (see [fallback behavior](#fallback-behavior)).
 
 #### String literal preservation { #string_literals }
 
-Formatting never changes what a string literal contains. Two mechanisms enforce this:
+Formatting never changes what a string literal contains. Four mechanisms enforce this:
 
 - PostgreSQL escape strings (`E'...'`) are held out of the sqlglot round trip entirely and restored byte-for-byte, keeping both their backslash escapes and their `E` prefix. This matters because sqlglot consumes backslash escapes inside an escape string without re-emitting them, which would turn `E'\\s+'` (a regex matching whitespace) into `e'\s+'` (a regex matching the letter `s`).
-- Every other literal — ordinary `'...'` strings and dollar-quoted bodies (`$$...$$`, `$tag$...$tag$`) — is compared before and after formatting. If any literal fails to come back unchanged, the statement is left unformatted rather than rewritten.
+- Indentation is never applied inside a multi-line literal — a dollar-quoted body (`$$...$$`, `$tag$...$tag$`) or an ordinary `'...'` string that spans lines. Leading whitespace on a continuation line is part of the stored value, not layout. The line that *opens* the literal is ordinary SQL and is indented with the statement around it, but every line from there to the closing delimiter is emitted exactly as written. Such a literal therefore keeps its original whitespace regardless of `--indent` or how deeply the statement is nested — which means its body will not line up visually with the statement that contains it. That is unavoidable: indenting it would change the string.
+- Commas are never moved into or out of a multi-line literal. `--leading-comma`, and the trailing-comma normalization that precedes it, both skip every line such a literal touches, including the line that opens it. A comma inside a multi-line string is data, so repositioning it would change the value rather than the layout.
+- Literals that do pass through sqlglot — ordinary single-line `'...'` strings — are compared before and after. If any fails to come back unchanged, the statement is left unformatted rather than rewritten.
 
-The second check is deliberately conservative: a statement may occasionally be left alone when the rewrite would in fact have been harmless (for example, sqlglot normalizes `interval '1 day'` to `INTERVAL '1 DAY'`, which changes the literal's text but not its meaning). Losing formatting on a statement is recoverable; silently changing what a query does is not.
+The last check is deliberately conservative: a statement may occasionally be left alone when the rewrite would in fact have been harmless (for example, sqlglot normalizes `interval '1 day'` to `INTERVAL '1 DAY'`, which changes the literal's text but not its meaning). Losing formatting on a statement is recoverable; silently changing what a query does is not.
 
-#### Fallback behavior
+#### Fallback behavior { #fallback-behavior }
 
-If sqlglot cannot parse a SQL statement, or if safety checks detect that formatting would corrupt the SQL — statement count changes, significant content loss, or an altered [string literal](#string_literals) — the original text is preserved unchanged.
+SQL that sqlglot cannot fully parse is left exactly as written. The parse is strict: if any statement in a run of SQL fails to parse, that whole run is emitted verbatim and only its indentation is normalized. Nothing partially understood is ever regenerated.
+
+That strictness is what keeps a clause from disappearing. Given a partial parse, sqlglot returns the fragment it did understand and drops the rest, so
+
+```sql
+INSERT INTO t (a, b)
+SELECT x, y FROM src
+CROSS JOIN LATERAL (VALUES (1, 2)) AS g(a, b)
+ON CONFLICT(a) DO NOTHING;
+```
+
+came back without its `DO NOTHING` — one statement in, one statement out, nearly all of the text intact, and no longer valid SQL. A dropped `DISTINCT`, `CASCADE`, `DESC`, or `NOT` costs even fewer characters, so no content-loss threshold can catch this class; only the parser knows whether it understood the whole statement.
+
+Formatting is also skipped when safety checks detect that it would corrupt SQL it did parse — statement count changes, significant content loss, or an altered [string literal](#string_literals). In every case the original text is preserved unchanged.
 
 Use `--no-sql` to skip SQL reformatting entirely and only normalize metacommands.
 
@@ -169,7 +184,7 @@ select id,name,created_at from users where active = true order by name;
 ```yaml
 repos:
   - repo: https://github.com/geocoug/execsql
-    rev: v2.22.5
+    rev: v2.22.7
     hooks:
       - id: execsql-format
 ```

{execsql2-2.22.5 → execsql2-2.22.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "execsql2"
-version = "2.22.5"
+version = "2.22.7"
 description = "Runs a SQL script against a PostgreSQL, SQLite, MariaDB/MySQL, DuckDB, Firebird, MS-Access, MS-SQL-Server, or Oracle database, or an ODBC DSN. Provides metacommands to import and export data, copy data between databases, conditionally execute SQL and metacommands, and dynamically alter SQL and metacommands with substitution variables."
 readme = { file = "README.md", content-type = "text/markdown" }
 license = { file = "LICENSE.txt" }
@@ -178,7 +178,7 @@ skip-magic-trailing-comma = false
 line-ending = "auto"
 
 [tool.bumpversion]
-current_version = "2.22.5"
+current_version = "2.22.7"
 commit = true
 tag = true
 tag_name = "v{new_version}"