Changelog¶

All notable changes to this project will be documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]¶

[1.22.1] - 2026-05-26¶

Changed¶

• Upper bounds removed from typer and pyyaml dependencies. Both are now pinned only by a lower bound (typer>=0.15, pyyaml>=6.0.1) so downstream projects can pick up newer releases without resolver conflicts. Resolved versions in the lock file move to typer 0.26.x and pyyaml 6.0.3.
• CLI exit code when invoked with no arguments is now 2 (was 0). Click 8.2+ standardized no_args_is_help to exit with the usage-error code; the help text is still printed. Scripts that previously checked pg-upsert; echo $? for 0 on a bare invocation must be updated.

[1.22.0] - 2026-04-20¶

Added¶

• QASeverity enum (ERROR / WARNING) added to the public API. Each QAError now carries a severity field (default ERROR), included in to_dict() and --output json. Programmatic consumers can filter by severity to distinguish blocking errors from informational warnings.
• --strict-columns CLI flag and strict_columns API parameter. When enabled, all missing staging columns are treated as errors (previous behavior). Defaults to False.

Changed¶

• qa_errors, qa_warnings, and qa_findings are now filtered properties. On TableResult, UpsertResult, and PipelineEvent, qa_errors returns ERROR-severity findings only (those that block the upsert). qa_warnings returns WARNING-severity findings only. qa_findings returns all findings combined. Previously qa_errors held every finding regardless of severity. The --output json response now includes separate qa_errors and qa_warnings arrays per table; the previous qa_errors array in that output now contains only ERROR-level items. PipelineEvent.qa_findings replaces what was formerly stored in PipelineEvent.qa_errors.
• Column existence checks are now severity-aware. Missing primary key columns and NOT NULL columns without a default are errors (they would cause the upsert to fail). All other missing columns produce warnings instead of errors. Warnings do not block qa_passed or the upsert pipeline. Use --strict-columns to restore the previous strict behavior.
• QA checks use savepoints for crash resilience. Each per-table check runs inside a PostgreSQL savepoint. If a check crashes (e.g. querying a column that doesn't exist in staging), the savepoint is rolled back, a warning is emitted, and subsequent checks continue normally. Previously a database error would abort the entire QA pipeline.
• QA summary displays three states. The summary panel and compact grid now show pass (green ✓), warning (yellow ⚠), and failure (red ✗) indicators. The footer line reports passed, warned, and failed counts separately.
• --check-schema exit code respects severity. The command now exits 0 when only warnings are present (previously any missing column caused exit 1).

Fixed¶

• Database crash when staging table is missing columns. Non-NULL, PK, FK, and check constraint checks queried columns from the base schema definition against the staging table without verifying the column existed in staging. This caused column "X" does not exist errors that aborted the entire QA pipeline. Each check now runs inside a savepoint — if it crashes, the error is caught, a warning is emitted, and subsequent checks continue.
• TableResult.qa_passed and PipelineEvent.qa_passed were severity-blind. Both used len(errors) == 0, causing UpsertResult.qa_passed to return False and the CLI to exit 1 even after a successful commit when only warnings were present. They now filter to ERROR severity only, matching PgUpsert._update_qa_passed().
• strict_columns config file key was not recognized. The CLI now accepts strict_columns in YAML config files (previously logged "Invalid configuration key will be ignored").

[1.21.0] - 2026-04-09¶

Added¶

• Diff highlighting in compare tables dialog: The interactive compare dialog shown before committing updates has a Highlight Diffs toggle button on both the Tkinter and Textual backends. Unchanged rows are tinted green, changed rows tan, and the specific cells that differ are prefixed with a ● marker. A summary line (N matching | N differing | 0 only in staging | 0 only in base) is always visible at the top of the dialog regardless of toggle state. Columns in exclude_cols are skipped from diff detection. Native Python equality (==) is used for comparison so type-equivalent values (e.g. Decimal("9.99") vs Decimal("9.9900")) do not produce false diffs.
• Fix sheet export for QA failures: --export-failures <dir> writes an actionable report of violating staging rows to a directory, in CSV (one file per table), JSON (single nested file), or XLSX (single workbook with sheet per table). Format is selected with --export-format csv|json|xlsx (default csv). Each unique staging row appears once (deduped by primary key) with an _issues column listing every problem found on that row and an _issue_types column for programmatic filtering. The _issues text includes primary key column names (e.g. "duplicate PK (book_id)") and foreign key target references (e.g. "FK violation: publisher_id -> public.publishers(publisher_id)"). Rows are sorted by primary key. Schema-level errors (missing columns, type mismatches) are routed to a separate _schema output. Row cap per check per table controlled by --export-max-rows (default 1000). CSV uses stdlib only; XLSX requires the optional openpyxl dependency (pip install pg-upsert[xlsx]).
• RowViolation and SchemaIssue dataclasses added to the public API (re-exported from pg_upsert). Populated on QAError.violations / QAError.schema_issues when capture_detail_rows=True. Each RowViolation carries pk_values, pk_columns, row_data, issue_type, issue_column, constraint_name, and description so programmatic consumers can build custom reports.
• "Running Without Constraints" documentation — new section in docs/qa_checks.md explaining how pg-upsert handles databases with no constraints: data QA checks pass vacuously and the upsert step skips tables without a primary key (with a warning). A note was also added to the README.
• API reference reorganized with section groupings (Main Entry Point, Result Objects, QA Error Models, Pipeline Callbacks and Context, Database Connection, Exceptions). Previously missing exported classes (CheckContext, CallbackEvent, PipelineEvent, PipelineCallback, PostgresDB, RowViolation, SchemaIssue) are now documented. Each class appears exactly once in the TOC (the previous config showed every class twice).
• PgUpsert constructor docs — docstring now documents all 17 parameters. ui_mode, compact, callback, capture_detail_rows, and max_export_rows were previously missing from the Args: section.
• pg-upsert.example.yaml now includes export_failures, export_format, and export_max_rows so users copying the example can discover the export feature.

Changed¶

• "Show mismatches" button removed from the Tkinter compare dialog. It duplicated (less usefully) what the new Highlight Diffs button does, and was non-functional for the pre-joined view pairs pg-upsert feeds into the dialog.
• QAError shape: the detail_rows/detail_headers fields added during the previous export rewrite are replaced with violations: list[RowViolation] and schema_issues: list[SchemaIssue]. QAError.to_dict() still excludes both, so --output json output is unchanged.
• Docs build: docs/pg_upsert.md no longer uses manual ## ClassName markdown headings above ::: blocks — mkdocstrings generates the symbol headings, avoiding duplicated TOC entries.

Fixed¶

• Config file loader crashed on Path(True) when YAML set export_failures: true (or similar non-string value). The loader now treats export_failures as a path-typed option alongside logfile: accepts str / Path, treats None / False / "" as unset, and rejects bool/int/other types with a clear error message before any DB connection is attempted.
• XLSX sheet name collisions — when two table names had the same first 31 characters, _write_xlsx silently overwrote the first sheet. It now tracks used sheet names and appends _2, _3, ... suffixes on collision, emitting a warning.
• PgUpsert.cleanup() now invalidates the per-table PK column cache (_qa._pk_cols_cache). Previously, running on the same instance after a schema change returned stale PK columns.
• _values_equal() in ui/diff.py caught Exception broadly, hiding programming errors. It now catches only TypeError / ValueError for the repr fallback.
• check_column_existence filtered empty fragments when splitting the control-table exclude_cols string. Previously, a trailing comma or col1,,col2 produced an empty-string entry in the exclude set.

[1.20.0] - 2026-04-04¶

Added¶

• Table progress counters in QA checks: Each QA check phase now shows [N/total] before the table name (e.g., ✓ [1/5] staging.genres). Progress counters appear when checks are run through run_all(), qa_all(), or any step-by-step qa_all_*() facade method. Single-table qa_one_*() calls omit the counter. Introduced CheckContext dataclass for structured progress context.

[1.19.0] - 2026-04-04¶

Fixed¶

• FK check SQL injection: Foreign key join conditions and column lists are now built with Identifier() in Python instead of using SQL() on string_agg output from the database. Prevents SQL corruption from tables with metacharacters in column names.
• Check constraint validation silently skipped for non-public schemas: Replaced conrelid::regclass::text (which returns schema-qualified names) with pg_class.relname (always returns bare table name), fixing silent CK check bypass when search_path doesn't include the base schema.
• FK error count underreported: FK violation count now sums all violation groups' nrows instead of reporting only the first group's count.
• FK error separator inconsistency: FK error strings now use ", " (comma + space) separator, consistent with other QA error types.
• QA summary panel rendered without color: _print_qa_summary_panel now uses rich.console.Group instead of str() joining, preserving Text object styling (bold, color) inside the Panel.
• run() did not catch psycopg2.Error: Database errors during run() now trigger a rollback and display an error message instead of leaving the connection in an aborted state.
• commit() did not guard on qa_passed: The step-by-step API (qa_all() → upsert_all() → commit()) now refuses to commit and rolls back when qa_passed is False, preventing accidental persistence of data that failed QA checks.
• qa_one_ck() missing table validation: Now calls _validate_table() before running check constraint checks, consistent with all other qa_one_* methods.
• in_transaction flag stale after reconnect: open_db() now resets in_transaction = False after a successful reconnection, preventing commit()/rollback() errors on reconnected connections.
• cleanup() left stale state: cleanup() now resets qa_passed and qa_errors after dropping temporary objects.
• Double console output: Fixed 5 locations across qa.py, upsert.py, executor.py, and control.py where the propagating module logger (logger.info/warning) duplicated messages already printed via the rich console. All user-facing messages now use display.console.print() + the file-only _file_logger.
• Step-by-step QA methods never set qa_passed: All individual qa_* methods (e.g., qa_all_null(), qa_one_pk()) now update qa_passed after each call via a new _update_qa_passed() helper. Previously only qa_all() and run() set the flag, so the step-by-step API chain could never reach commit().
• upsert_all() proceeded after failed QA: upsert_all() now refuses to execute when qa_passed is False, matching the documented contract that "loading is not attempted" when QA fails. Previously it only logged a warning.
• FK check silent on tables with no foreign keys: check_fks now prints a ✓ pass line for tables that have no FK constraints, consistent with all other QA checks.
• CK check printed ✓ for tables with no check constraints via fallthrough: check_cks now explicitly returns early with a pass line when ups_sel_cks is empty, matching the FK check pattern.
• Unique constraint check issued redundant DB query: check_unique now computes error totals from already-fetched rows in Python instead of running a second SELECT count(*), sum(nrows) query.
• CLI URI built by string concatenation: Special characters in --user, --host, or --database values are now properly percent-encoded with urllib.parse.quote(), preventing malformed URIs.
• CLI except Exception swallowed tracebacks: The top-level exception handler now catches expected errors (ValueError, psycopg2.Error, OSError, yaml.YAMLError) specifically, and logs the traceback at DEBUG level for unexpected errors.
• Dead hl_both_var assignment in TableUI.activate(): Removed a stale line that set self.hl_both_var = None — a variable that only exists on CompareUI.
• Debug logging opened unnecessary cursors: executor.py debug logging now uses as_string(self.db.conn) instead of as_string(self.db.cursor()) to avoid opening and discarding a cursor for each log call.

Changed¶

• __init__.py no longer imports CLI app: from .cli import app was removed from __init__.py to avoid pulling typer, pyyaml, and other CLI dependencies into every from pg_upsert import PgUpsert call. The app object is now only imported in __main__.py.

Removed¶

• print_upsert_summary(): Removed unused display function and its 6 tests. The upsert summary is rendered inline by _do_commit().
• Dead table_num/total_tables parameters: Removed from print_check_table_pass() and print_check_table_fail() — never passed by any caller.

[1.18.2] - 2026-04-03¶

Fixed¶

• Foreign key check interactive UI (tkinter/textual) now shows all violation rows instead of only the first row. Console and logfile output were unaffected.

[1.18.1] - 2026-04-03¶

Changed¶

• Updated CLI description to match GitHub project description.
• Updated example screenshot.

[1.18.0] - 2026-04-03¶

Added¶

• PgUpsert.cleanup() method — explicitly drops all ups_* temporary tables and views created during the pipeline. Useful for long-lived connections where you want to reclaim temp object space without closing the connection.
• callback parameter on PgUpsert — optional callable that fires QA_TABLE_COMPLETE and UPSERT_TABLE_COMPLETE events during the pipeline. Return False from the callback to abort with rollback. New types: CallbackEvent, PipelineEvent, PipelineCallback.

Fixed¶

• Removed stale docstring in QARunner.check_nulls() referencing nonexistent temporary objects.

[1.17.0] - 2026-04-03¶

Changed¶

• All QA check methods now print pass/fail output individually via display.print_check_table_pass() / display.print_check_table_fail(). Previously, pass output was only produced when checks were run through run_all() — standalone calls (e.g., qa_column_existence(), qa_type_mismatch()) were silent on success.

[1.16.1] - 2026-04-03¶

Fixed¶

• PostgresDB.__del__() and close() no longer close externally-provided connections (conn=). Only connections created by PostgresDB itself are closed. Previously, garbage collection of a PgUpsert instance would close the caller's connection.

[1.16.0] - 2026-04-03¶

Added¶

• PgUpsert.qa_errors attribute — accumulates QAError instances from any QA method (qa_all(), qa_column_existence(), qa_type_mismatch(), individual qa_one_*() methods, etc.). Enables programmatic inspection of QA results without requiring a full run() call.
• UpsertResult now includes staging_schema, base_schema, upsert_method, started_at, finished_at, and duration_seconds in to_dict()/to_json() output.
• PGPASSWORD environment variable support for non-interactive authentication (standard PostgreSQL convention).
• --output json now suppresses all console output — only clean JSON on stdout.
• --encoding documented in README CLI options table.
• Authentication section in README explaining password resolution order.

Fixed¶

• Fixed elapsed_time() calling datetime.now() twice — now uses cached value.
• Narrowed except Exception to specific exception types in postgres.py and upsert.py.
• Fixed stale docstring reference to pg_upsert.ui_console → pg_upsert.ui.console.

[1.15.0] - 2026-04-02¶

Added¶

• pg-upsert version and PostgreSQL version now logged in logfile header.
• Progress counters in QA check output: phase (3/7) in section headers, table [1/5] on pass lines.
• Logfile run header/footer with ==== separators and timestamps for easy navigation in appended logs.
• Table count shown in "Tables selected for upsert" message.
• Exit code 1 when QA checks fail — CI pipelines can detect failures without parsing output.
• New docs/architecture.md — module structure, pipeline flow, design decisions for contributors.
• API reference now documents UpsertResult, TableResult, QAError, QACheckType, UserCancelledError.
• --docs added to CLI options table in README.
• Exit Codes section in README.

Changed¶

• README config file example updated to show all available options.
• Config file now supports output, check_schema, compact, ui_mode keys.
• Dockerfile: removed tkinter GUI deps (useless in Docker), installs [tui] extra (textual) instead. Added OCI labels.

[1.14.0] - 2026-04-02¶

Added¶

• --compact CLI flag for grid-style QA summary (✓/✗ per check type per table).
• Composite UNIQUE constraint (uq_books_title_genre) added to test schemas.
• Tests: composite UNIQUE violations, empty staging table edge cases (null/pk/unique/upsert with 0 rows), FK dependency ordering validation.
• 263 total tests, 93% coverage.

Changed¶

• Removed --quiet CLI flag (no longer functional — all output goes through rich console).

Fixed¶

• Fixed open_db reconnect fragility — now stores original URI at init time for reliable reconnection instead of regex-based URI reconstruction.

[1.13.1] - 2026-04-02¶

Fixed¶

• Fixed check constraint output using bare logger.warning instead of rich ✗ formatting — now consistent with all other check types.
• Removed docs/index.md from git tracking (auto-generated from README.md by justfile/RTD build).

[1.13.0] - 2026-04-02¶

Added¶

• 91 new tests: test_models.py, test_display.py, test_ui_factory.py, test_console_backend.py, facade method tests. Total: 256 tests, 93% coverage.

Changed¶

• Rewrote docs/examples.md with current output format (rich ✓/✗ indicators, summary layout, UpsertResult JSON examples).
• Optimized check_nulls() from N+1 queries (one per column) to a single SUM(CASE WHEN ... IS NULL) query.
• Replaced all SQL() wrapping of DB-derived strings in executor.py with proper Identifier() composition for column lists, join expressions, SET clauses, and PK lists.

Fixed¶

• Fixed exclude_null_check_cols generating invalid NOT IN ('') SQL when the exclusion list is empty — now conditionally includes the clause only when columns are specified.

[1.12.0] - 2026-04-02¶

Added¶

• Start and end timestamps with elapsed duration logged for every run() invocation.
• Row matching in Textual TUI comparison view — clicking a row in either table scrolls to the matching PK row in the other table.
• New documentation page: QA Checks Reference (docs/qa_checks.md) with PostgreSQL documentation links.
• Codecov badge in README.

Changed¶

• BREAKING: Removed __version__.py — version is now read from package metadata via importlib.metadata.version("pg_upsert") at runtime.
• BREAKING: --tables CLI option renamed to --table (singular, since each flag specifies one table).
• Reorganized source into ui/ subpackage: ui/base.py, ui/factory.py, ui/console.py, ui/tkinter_backend.py, ui/textual_backend.py, ui/display.py, ui/legacy.py.
• Textual comparison view row matching now uses RowHighlighted event (matching execsql's pattern) instead of CursorChanged. Pre-builds PK→row-index maps at mount time for O(1) lookup.
• Password prompt shows rich-formatted connection info: PostgreSQL → user@host:port/db.
• Invalid schema/table errors show rich ✗ formatting.
• "Tables selected for upsert" shown as labeled list with staging → public context.
• --check-schema output uses rich section header, per-table ✓/✗, and bold summary.
• All CLI validation errors use consistent rich formatting via _cli_error() helper.
• --ui validated before password prompt to avoid unnecessary prompting.
• Logfile appends instead of being deleted and recreated on each run.
• Display logger uses propagate=False to prevent duplicate console output.
• Removed console as a public --ui option — console backend is internal-only for non-interactive runs.
• Updated README: complete rewrite with CLI options table, fixed parameter names, documented UpsertResult.
• Updated pyproject.toml description, removed markdown-include dependency.
• docs/index.md auto-generated from README.md via justfile/RTD build.

Fixed¶

• Fixed _validate_schemas and _validate_table executing same query twice — now caches cursor result.
• Guarded all next(iter()) calls against StopIteration — replaced with [0] indexing or added safety comments.
• Fixed strict=False in ui/console.py zip — now strict=True.
• Fixed broad except Exception in config file loading — now catches yaml.YAMLError, OSError.
• Fixed misleading "No columns found in base table" log message — now says "No shared columns".
• Fixed dead code: unreachable else branch in postgres.py rowdict encoding check.

Removed¶

• src/pg_upsert/__version__.py — version, title, description, and other metadata are no longer maintained in a separate file.
• markdown-include dependency (no longer used after docs migration to zensical).

[1.11.2] - 2026-04-02¶

Added¶

• Green ✓ checkmarks now shown for QA checks that pass, not just ✗ for failures. Gives users confidence that checks actually ran.

[1.11.1] - 2026-04-02¶

Changed¶

• All display.print_* functions now dual-write: rich output to console (stderr) and plain-text equivalent to the logger (logfile). Console and logfile are always in sync.
• All QA check types (null, column existence, type mismatch) now use consistent ✗ prefix via print_check_table_fail(), matching PK/FK/UNIQUE/CK checks.
• QA summary supports compact grid mode via compact=True parameter — shows ✓/✗ per check type per table in a minimal grid.

[1.11.0] - 2026-04-02¶

Added¶

• ui_base.py — UIBackend abstract base class defining show_table() and show_comparison() for all interactive dialogs.
• ui_console.py — ConsoleBackend: non-interactive backend that renders tables via rich and auto-continues (returns 0) without prompting.
• ui_tkinter.py — TkinterBackend: wraps the existing TableUI and CompareUI from ui.py with lazy tkinter import, fixing headless import failures.
• ui_textual.py — TextualBackend: full-terminal TUI dialogs using textual DataTable and Button widgets.
• ui_factory.py — get_ui_backend(ui_mode) factory supporting "auto", "console", "tkinter", and "textual" modes. Auto-detection uses DISPLAY/WAYLAND_DISPLAY environment variables.
• --ui CLI option: select UI backend (auto, console, tkinter, textual).
• ui_mode parameter on PgUpsert.__init__ to control backend selection programmatically.
• textual>=0.47.0 added as an optional tui extra and a dev dependency.

Changed¶

• ControlTable, QARunner, and UpsertExecutor now accept a ui: UIBackend | None parameter; all TableUI/CompareUI calls replaced with self._ui.show_table() / self._ui.show_comparison().
• PgUpsert creates the UI backend once and shares it with all sub-components.
• Non-interactive runs are always routed through ConsoleBackend regardless of ui_mode.
• ui_tkinter.py and ui_textual.py added to coverage omit list (require event loop to test).

[1.10.0] - 2026-04-02¶

Added¶

• New display.py module — rich-based output formatting with rich.table.Table, rich.panel.Panel, and colored pass/fail indicators.
• print_qa_summary() — compact per-table QA results with pass/fail status and indented error details.
• print_check_start(), print_check_table_pass(), print_check_table_fail() — consistent check-level output formatting.
• print_upsert_summary() — clean upsert results table with per-table row counts and totals.

Changed¶

• Replaced tabulate dependency with rich for all data table rendering. Tables now auto-size, have box borders, and support color.
• QA check output now uses colored status indicators (green ✓ / red ✗) instead of raw markdown tables.
• QA error summary uses a vertical per-table layout instead of one wide table — much easier to read.
• rich is now an explicit direct dependency (was previously transitive via typer).

Removed¶

• Removed tabulate dependency.
• Removed _tabulate_sql() helper methods from qa.py, control.py, and upsert.py.

[1.9.2] - 2026-04-02¶

Added¶

• Test data for column existence and type mismatch failures in schema_failing.sql — staging books is missing the notes column, staging publishers.publisher_name is integer (vs varchar in base).

[1.9.1] - 2026-04-02¶

Fixed¶

• Fixed UNIQUE constraint check incorrectly flagging multiple NULL values as duplicates. PostgreSQL allows multiple NULLs in UNIQUE columns; the check now excludes rows with NULL values in constrained columns.

[1.9.0] - 2026-04-02¶

Added¶

• --output=json CLI flag — outputs UpsertResult as machine-parseable JSON to stdout. Log messages are suppressed when JSON output is enabled.
• --check-schema CLI flag — pre-flight validation mode that runs column existence and type mismatch checks only, then exits. Exit code 0 = compatible, 1 = issues found. Works with --output=json.

[1.8.0] - 2026-04-02¶

Added¶

• UNIQUE constraint QA checks — new check_unique() method detects duplicate values in UNIQUE-constrained columns (not just primary keys). Uses pg_constraint contype='u'.
• Column existence validation — new check_column_existence() method flags base table columns missing from the staging table. Respects exclude_cols setting.
• Column type mismatch detection — new check_type_mismatch() method detects hard type incompatibilities between staging and base columns using PostgreSQL's pg_cast catalog. Only flags types with no implicit or assignment cast.
• New control table columns: unique_errors, column_errors, type_errors.
• New facade methods on PgUpsert: qa_all_unique(), qa_one_unique(), qa_column_existence(), qa_type_mismatch().
• UNIQUE constraint (uq_authors_email) added to test schema authors.email column.

Changed¶

• QA check ordering: column existence and type mismatch checks now run before data checks (null, PK, unique, FK, CK) to catch schema issues early.

[1.7.0] - 2026-04-02¶

Added¶

• UpsertResult dataclass — run() now returns structured results with qa_passed, total_updated, total_inserted, to_dict(), and to_json() methods.
• TableResult dataclass — per-table stats and QA errors.
• QAError dataclass — individual QA finding with table name, check type, and details.
• QACheckType enum — types of QA checks (null, pk, unique, fk, ck, type_mismatch, column_existence).
• New modules: control.py (ControlTable), qa.py (QARunner), executor.py (UpsertExecutor), models.py (dataclasses).

Changed¶

• BREAKING: run() now returns UpsertResult instead of self. This is a breaking change for callers that chained methods after run(), but run() is designed as a terminal call.
• Decomposed the 2,100-line PgUpsert class into focused modules: QARunner (QA checks), UpsertExecutor (upsert operations), ControlTable (temp table management). PgUpsert is now a thin facade preserving the existing constructor API.
• Replaced while-True/processed-flag database loops with Python iteration in QA checks.
• qa_one_ck() now updates the control table directly, consistent with qa_one_null/pk/fk.
• Config file no longer silently overrides explicit CLI arguments — CLI args take precedence.
• Password is no longer embedded in the connection URI; extracted and stored separately for reconnection.

Fixed¶

• Fixed rows_updated count — now uses cursor.rowcount from the actual UPDATE execution instead of the staging match count.
• Fixed _validate_schemas() executing the same query twice.
• Fixed open_db() unreachable dead code branch and reconnection failure.

[1.6.1] - 2026-04-02¶

[1.6.0] - 2026-04-02¶

Added¶

• UserCancelledError exception — exported from pg_upsert for callers that use the library as an import.
• CHANGELOG.md — Keep a Changelog format, seeded from git tag history.
• justfile — Task automation recipes (sync, lint, test, docs, bump).
• CONTRIBUTING.md — Development setup, available recipes, testing, and release process.
• SECURITY.md — Vulnerability reporting policy.
• .python-version — Pin to Python 3.13.
• .github/PULL_REQUEST_TEMPLATE.md — PR checklist template.
• Python 3.14 support added to CI matrix and classifiers.
• macOS and Windows unit-test jobs in CI (no database required).
• Codecov coverage upload in CI.
• Comprehensive test suite rewrite — 149 tests covering QA checks (null, PK, FK, check constraints), upsert operations, interactive mode, failing data scenarios, CLI argument parsing, config file handling, and PostgresDB connection management. Tests auto-skip when no database is available. Coverage at 91%.

Changed¶

• Switched build system from setuptools to Hatchling.
• Migrated documentation from MkDocs to Zensical.
• Updated .readthedocs.yaml for Zensical build pipeline.
• Updated pre-commit hooks to latest versions; added uv-pre-commit (lockfile management) and mdformat (markdown formatting).
• Updated CI/CD workflow: concurrency groups, twine check, updated action versions.
• Interactive cancellation now raises UserCancelledError instead of calling sys.exit(0), allowing proper transaction rollback and library use as an import.
• Updated .gitignore with organized sections and Zensical/uv patterns.
• Ruff target version set to py310 (minimum supported) instead of py313.
• Test coverage floor set to 80%.

Fixed¶

• Fixed exclude columns whitespace bug — split(",") now strips whitespace so "col1, col2" no longer produces " col2" with a leading space.
• Fixed qa_passed not being reset between run() calls — a second run() on the same PgUpsert instance could skip QA failures from the first run.
• Fixed rich.print shadowing the Python builtin print in cli.py — renamed import to rprint.
• Fixed qa_one_pk() returning None instead of self when table has no primary key — broke method chaining.
• Fixed CLI ignoring --encoding argument — was hardcoded to "utf-8" instead of using the user-provided value.
• Removed unused imports (__description__, __version__) from upsert.py, postgres.py, and ui.py.
• Removed dead commented-out code in upsert.py.

[1.5.3] - 2025-02-12¶

Fixed¶

• Fixed release action permissions.

[1.5.2] - 2025-02-12¶

Fixed¶

• Fixed bumpversion file path configuration.
• Updated CI/CD to auto-generate release notes.

[1.5.1] - 2025-01-15¶

Changed¶

• Updated Docker build to use Python 3.13 alpine image.
• Updated Docker section in README.
• Updated pre-commit hooks, added typos hook.
• Updated host in pg-upsert.example.yaml for Docker-specific runs.

[1.5.0] - 2025-01-15¶

Changed¶

• Converted CLI from argparse to Typer.
• Renamed stg_schema parameter to staging_schema for consistency.
• Synced CLI argument descriptions with help text.

Added¶

• CLI tests.

[1.4.6] - 2024-12-16¶

Fixed¶

• Fixed badge URL.
• Set build and publish jobs to run only on tag push.

[1.4.5] - 2024-12-16¶

Changed¶

• Updated documentation.
• Renamed PgUpsert._show() to PgUpsert._tabulate_sql().

Added¶

• Added PgUpsert.show_control() method.

[1.4.4] - 2024-12-15¶

Changed¶

• Updated documentation and examples.
• Applied custom debug log formatting.
• Switched to uv-based build.

Added¶

• More tests.

[1.4.3] - 2024-11-13¶

Fixed¶

• Fixed indentation issue.

[1.4.2] - 2024-11-13¶

Changed¶

• Auto-updated pre-commit hooks.
• Removed __del__ method.
• Refined dependency version requirements.

[1.4.1] - 2024-11-13¶

Added¶

• Added PyYAML as a dependency.

Fixed¶

• Removed unused imports.
• Fixed requirements.txt.

[1.4.0] - 2024-11-12¶

Added¶

• Database connection parameters via individual host/port/user/database options.
• YAML configuration file support.

[1.3.1] - 2024-10-29¶

Fixed¶

• Fixed tag push conditional in CI/CD.

[1.3.0] - 2024-10-29¶

Changed¶

• CLI reconfiguration.
• Stream FK and PK errors to console and log file.

[1.2.8] - 2024-10-03¶

Changed¶

• Reconfigured package logging.
• Renamed _version.py to __version__.py.

[1.2.7] - 2024-07-29¶

Changed¶

• Switched documentation from Sphinx to MkDocs.

[1.2.6] - 2024-07-23¶

Changed¶

• Version bump release.

[1.2.5] - 2024-07-23¶

Changed¶

• Updated project links.

[1.2.4] - 2024-07-22¶

Fixed¶

• Wrapped CLI entrypoint in try/except block.

[1.2.3] - 2024-07-22¶

Changed¶

• Updated README examples.
• Added docs status badge.

[1.2.2] - 2024-07-20¶

Fixed¶

• Fixed invalid routine call.

[1.2.1] - 2024-07-19¶

Changed¶

• Version bump release.

[1.2.0] - 2024-07-19¶

Changed¶

• Version bump release.

[1.1.4] - 2024-07-17¶

Changed¶

• Version bump release.

[1.1.3] - 2024-07-17¶

Changed¶

• Version bump release.

[1.1.2] - 2024-07-17¶

Changed¶

• Version bump release.

[1.1.1] - 2024-07-17¶

Changed¶

• Version bump release.

[1.1.0] - 2024-07-17¶

Changed¶

• Version bump release.

[1.0.0] - 2024-07-17¶

Added¶

• Initial stable release.
• PostgreSQL upsert functionality with staging/base table support.
• NOT NULL, PRIMARY KEY, FOREIGN KEY, and CHECK CONSTRAINT validation.
• Interactive confirmation mode.
• CLI interface.
• Python API.
• MkDocs documentation.

[0.0.9] - 2024-06-10¶

Changed¶

• Pre-release version.

[0.0.8] - 2024-06-10¶

Changed¶

• Pre-release version.

[0.0.7] - 2024-06-10¶

Added¶

• Initial pre-release.