sqlmesh-hardcharger 1.0.0__tar.gz

sqlmesh_hardcharger-1.0.0/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+## [1.0.0] - 2026-10-23
+
+- Initial Hardcharger release, ported from sqlmesh-gizmosql 0.3.1 with all 55 inherited tests.
+- Native Hardcharger ADBC 2.0.2 over Warp SQL HTTP(S), TLS by default, Python 3.11+.
+- SQLMesh 0.236.4, the latest compatible transitive dependencies, refreshed development/build tools and lockfile.
+- Reuse SQLMesh's current DuckDB implementation, including DuckLake partitioning and case-insensitive cascade detection.
+- Fix partial source-column ingestion, typed missing values, native transaction handling, metadata discovery and quoted schema names.
+- Add token/mTLS/custom CA options, per-connection default catalogs, IPv6 and a YAML-aware SQLMesh CLI.
+- Add regression coverage and current upstream DuckDB/shared engine tests against real Hardcharger.
+- Tag-gated PyPI Trusted Publishing with provenance attestations and GitHub release artifacts.
+
+Earlier GizmoSQL releases remain in the preserved Git history and original repository.

sqlmesh_hardcharger-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright Contributors to the SQLMesh project
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

sqlmesh_hardcharger-1.0.0/MANIFEST.in

@@ -0,0 +1,5 @@
+include CHANGELOG.md Makefile uv.lock
+recursive-include docs *.md *.png
+recursive-include scripts *.py
+recursive-include tests *.py *.yaml
+global-exclude *.py[cod] *.db *.duckdb *.wal *.log

sqlmesh_hardcharger-1.0.0/Makefile

@@ -0,0 +1,45 @@
+.PHONY: install install-dev test unit-test integration-test ducklake-test all-tests upstream-test lint format build docker-up docker-down
+
+COMPOSE = docker compose -p sqlmesh-hardcharger -f tests/integration/docker/compose.hardcharger.yaml
+
+install:
+	uv sync
+
+install-dev:
+	uv sync --extra dev --frozen
+
+test: unit-test
+
+unit-test:
+	uv run pytest -m "not integration"
+
+integration-test:
+	uv run pytest -m "integration and not ducklake"
+
+docker-up:
+	$(COMPOSE) up -d --wait
+
+docker-down:
+	$(COMPOSE) down
+
+ducklake-test: docker-up
+	POSTGRES_HOST=127.0.0.1 POSTGRES_PORT=55441 uv run pytest -m ducklake
+
+all-tests: docker-up
+	POSTGRES_HOST=127.0.0.1 POSTGRES_PORT=55441 uv run pytest -m "integration or not integration"
+
+upstream-test:
+	uv run python scripts/test-upstream.py
+
+lint:
+	uv run ruff check .
+	uv run ruff format --check .
+	uv run mypy sqlmesh_hardcharger
+
+format:
+	uv run ruff check --fix .
+	uv run ruff format .
+
+build:
+	uv run python -m build
+	uv run twine check --strict dist/*

sqlmesh_hardcharger-1.0.0/PKG-INFO

@@ -0,0 +1,178 @@
+Metadata-Version: 2.4
+Name: sqlmesh-hardcharger
+Version: 1.0.0
+Summary: Hardcharger engine adapter for SQLMesh
+Author-email: Philip Moore <philip@gizmodata.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/gizmodata/sqlmesh-hardcharger
+Project-URL: Repository, https://github.com/gizmodata/sqlmesh-hardcharger
+Project-URL: Documentation, https://github.com/gizmodata/sqlmesh-hardcharger#readme
+Keywords: sqlmesh,hardcharger,duckdb,arrow,warp-sql,data-engineering
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Database
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: sqlmesh<0.237,>=0.236.4
+Requires-Dist: adbc-driver-hardcharger<3,>=2.0.2
+Provides-Extra: dev
+Requires-Dist: pytest>=9.1.1; extra == "dev"
+Requires-Dist: pytest-cov>=7.1.0; extra == "dev"
+Requires-Dist: mypy>=2.4.0; extra == "dev"
+Requires-Dist: ruff>=0.17.2; extra == "dev"
+Requires-Dist: hardcharger>=2.0.1; extra == "dev"
+Requires-Dist: pytest-mock>=3.17.0; extra == "dev"
+Requires-Dist: pytest-xdist>=3.8.0; extra == "dev"
+Requires-Dist: build>=1.6.1; extra == "dev"
+Requires-Dist: twine>=7.0.0; extra == "dev"
+Dynamic: license-file
+
+<p align="center">
+  <a href="https://github.com/gizmodata/hardcharger">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/gizmodata/sqlmesh-hardcharger/main/docs/assets/hardcharger-banner-dark.png">
+      <img src="https://raw.githubusercontent.com/gizmodata/sqlmesh-hardcharger/main/docs/assets/hardcharger-banner-light.png" alt="Hardcharger™" width="400">
+    </picture>
+  </a>
+</p>
+
+<h1 align="center">SQLMesh Hardcharger™ Adapter</h1>
+
+<p align="center">
+  <a href="https://github.com/gizmodata/sqlmesh-hardcharger/actions/workflows/ci.yml"><img src="https://github.com/gizmodata/sqlmesh-hardcharger/actions/workflows/ci.yml/badge.svg" alt="CI: full suite on Python 3.11–3.14"></a>
+  <a href="https://pypi.org/project/sqlmesh-hardcharger/"><img src="https://img.shields.io/pypi/v/sqlmesh-hardcharger?logo=pypi" alt="PyPI version"></a>
+  <a href="https://pypi.org/project/sqlmesh-hardcharger/"><img src="https://img.shields.io/badge/Python-3.11–3.14-3776AB?logo=python&amp;logoColor=white" alt="Python 3.11–3.14"></a>
+  <a href="https://pypi.org/project/sqlmesh-hardcharger/"><img src="https://img.shields.io/pepy/dt/sqlmesh-hardcharger.svg" alt="PyPI downloads"></a>
+  <a href="https://github.com/gizmodata/hardcharger-adbc"><img src="https://img.shields.io/badge/driver-Hardcharger%20ADBC-f15a24.svg" alt="Hardcharger ADBC driver"></a>
+  <a href="https://github.com/gizmodata/warp-sql"><img src="https://img.shields.io/badge/protocol-Warp%20SQL-31a8db.svg" alt="Warp SQL protocol"></a>
+  <a href="https://github.com/gizmodata/sqlmesh-hardcharger/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-brightgreen.svg" alt="Apache 2.0 license"></a>
+  <a href="https://gizmodata.com"><img src="https://img.shields.io/badge/by-GizmoData%E2%84%A2-f15a24.svg" alt="GizmoData™"></a>
+</p>
+
+
+Run [SQLMesh](https://sqlmesh.com) transformations on [Hardcharger™](https://gizmodata.com/hardcharger), GizmoData's DuckDB 2.0 server. Connect using the native [Hardcharger ADBC driver](https://github.com/gizmodata/hardcharger-adbc) over **Warp SQL HTTP(S)**.
+
+## Install
+
+```bash
+pip install sqlmesh-hardcharger
+```
+
+Python **3.11 or later**. Installs SQLMesh 0.236.4 (compatible 0.236.x releases) and `adbc-driver-hardcharger>=2.0.2,<3`. SQLGlot stays within SQLMesh's supported 30.8.x range. The local DuckDB package is SQLMesh's dependency; remote queries execute on the Hardcharger server's DuckDB 2.0 engine.
+
+## Quick start
+
+Add `config.yaml` to your SQLMesh project:
+
+```yaml
+gateways:
+  hardcharger:
+    connection:
+      type: hardcharger
+      host: localhost
+      port: 31337
+      username: "{{ env_var('HARDCHARGER_USERNAME') }}"
+      password: "{{ env_var('HARDCHARGER_PASSWORD') }}"
+      use_encryption: true
+      # database: analytics  # optional existing default catalog
+    state_connection:
+      type: duckdb
+      database: sqlmesh_state.duckdb
+
+default_gateway: hardcharger
+model_defaults:
+  dialect: duckdb
+```
+
+Use the included CLI, which registers the adapter **before** SQLMesh loads YAML:
+
+```bash
+sqlmesh-hardcharger info
+sqlmesh-hardcharger plan
+sqlmesh-hardcharger run
+```
+
+It exposes SQLMesh's standard commands and options. For a local server without TLS, explicitly set `use_encryption: false`; otherwise HTTPS and certificate verification are enabled. The adapter builds `hardcharger://host:port` URIs, adding `?tls=false` only for plaintext.
+
+For the standard `sqlmesh` command, import `sqlmesh_hardcharger` in a Python `config.py` before constructing your SQLMesh `Config`. For Python applications:
+
+```python
+import sqlmesh_hardcharger  # registers type: hardcharger
+from sqlmesh import Context
+
+context = Context(paths="path/to/project")
+try:
+    context.plan(auto_apply=True, no_prompts=True)
+finally:
+    context.close()
+```
+
+Use a separate PostgreSQL state connection for production, following [SQLMesh's state connection guidance](https://sqlmesh.readthedocs.io/en/stable/guides/configuration/#state-connection). The local DuckDB state connection above is for development. The tests also exercise state migrations on Hardcharger, but SQLMesh does not recommend this custom engine for production state storage.
+
+## Features
+
+- DuckDB SQL generation, SQLMesh plan/apply/run, incremental models, logical merges, SCD type 2 and table diffs.
+- Arrow-native bulk DataFrame ingestion, including partial source columns, typed nulls and reordered columns.
+- Native ADBC transactions and nested SQLMesh transaction scopes, with rollback on errors.
+- Catalog discovery and switching, automatic schema creation, quoted identifiers and non-default catalogs.
+- DuckLake with PostgreSQL metadata, partitioning and correct cascade behavior, inherited from current SQLMesh.
+- Password, bearer token, browser OAuth/SSO, trusted external identity token and mutual TLS authentication through the native driver.
+
+## Connection options
+
+| Option | Default | Meaning |
+| --- | --- | --- |
+| `host` | `localhost` | Server hostname or IPv6 address |
+| `port` | `31337` | Warp SQL port (1–65535) |
+| `username`, `password` | unset | Password sign-in |
+| `access_token` | unset | Hardcharger bearer token; omit password credentials |
+| `subject_token` | unset | Trusted identity-provider token for token exchange; omit other credentials |
+| `auth_type` | unset (password) | `password`, `external`, `client_certificate` or `mtls` |
+| `use_encryption` | `true` | HTTPS; false explicitly opts into plain HTTP |
+| `disable_certificate_verification` | `false` | Development-only TLS verification bypass |
+| `tls_root_certs` | unset | PEM CA text or file path |
+| `tls_client_cert`, `tls_client_key` | unset | PEM text or paths for mTLS |
+| `tls_server_name` | unset | Certificate hostname / SNI override |
+| `database` | unset | Existing catalog to select on each new connection |
+| `concurrent_tasks` | `4` | Concurrent SQLMesh tasks |
+| `register_comments` | `true` | Register model comments |
+| `pre_ping` | `false` | Check pooled connections before use |
+
+For browser sign-in, set `auth_type: external` and omit username/password/token. For client-certificate sign-in, set `auth_type: client_certificate`, provide the certificate and key, and omit password/token credentials. See the [driver authentication documentation](https://github.com/gizmodata/hardcharger-adbc/tree/main/python).
+
+Catalog creation attaches a DuckDB file on the **server**. Dropping a catalog detaches it; it never deletes a file on the client or deletes the server's database file. Manage server files through your server administration process. Materialized views, managed models, SQLMesh grant synchronization and custom `when_matched` logical merge clauses are not advertised by this adapter.
+
+## Development and testing
+
+```bash
+uv sync --extra dev --frozen
+uv run ruff check .
+uv run mypy sqlmesh_hardcharger
+uv run pytest  # unit tests
+
+# All inherited and Hardcharger-specific integration tests, including DuckLake:
+docker compose -p sqlmesh-hardcharger -f tests/integration/docker/compose.hardcharger.yaml up -d --wait
+POSTGRES_HOST=127.0.0.1 POSTGRES_PORT=55441 uv run pytest -m integration
+
+# Current upstream DuckDB and shared engine tests, over a real Hardcharger server:
+uv run python scripts/test-upstream.py
+```
+
+The `hardcharger` development dependency downloads and verifies the released server binary on first use. Override it with `HARDCHARGER_SERVER_BINARY` when testing another build. A server is required for integration tests: they fail instead of silently skipping if it cannot start.
+
+All 55 tests from [sqlmesh-gizmosql](https://github.com/gizmodata/sqlmesh-gizmosql/tree/0f4c37e91677b10e0a053cabea812de2ab31403a) are retained. The upstream runner pins SQLMesh v0.236.4 at `f6527ffbd8d54d91e26fab7d36c8f4a061bc6451`, uses the installed SQLMesh package, and replaces connection fixtures without changing assertions. Only the two MotherDuck-specific unit tests are deselected; the upstream suite's own unsupported-feature skips remain visible. Bump the pin and dependency range together when adopting a new SQLMesh API series.
+
+CI tests Python 3.11–3.14, runs the upstream compatibility job, checks types and lint, builds the wheel/sdist, and publishes from version tags using PyPI Trusted Publishing with attestations. See [release setup](docs/releasing.md).
+
+## License and origin
+
+Apache-2.0. Adapted from GizmoData's SQLMesh GizmoSQL adapter, preserving its Git history and tests. DuckDB engine semantics are inherited from Apache-2.0 SQLMesh. Hardcharger and GizmoData are trademarks of GizmoData.

sqlmesh_hardcharger-1.0.0/README.md

@@ -0,0 +1,140 @@
+<p align="center">
+  <a href="https://github.com/gizmodata/hardcharger">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/gizmodata/sqlmesh-hardcharger/main/docs/assets/hardcharger-banner-dark.png">
+      <img src="https://raw.githubusercontent.com/gizmodata/sqlmesh-hardcharger/main/docs/assets/hardcharger-banner-light.png" alt="Hardcharger™" width="400">
+    </picture>
+  </a>
+</p>
+
+<h1 align="center">SQLMesh Hardcharger™ Adapter</h1>
+
+<p align="center">
+  <a href="https://github.com/gizmodata/sqlmesh-hardcharger/actions/workflows/ci.yml"><img src="https://github.com/gizmodata/sqlmesh-hardcharger/actions/workflows/ci.yml/badge.svg" alt="CI: full suite on Python 3.11–3.14"></a>
+  <a href="https://pypi.org/project/sqlmesh-hardcharger/"><img src="https://img.shields.io/pypi/v/sqlmesh-hardcharger?logo=pypi" alt="PyPI version"></a>
+  <a href="https://pypi.org/project/sqlmesh-hardcharger/"><img src="https://img.shields.io/badge/Python-3.11–3.14-3776AB?logo=python&amp;logoColor=white" alt="Python 3.11–3.14"></a>
+  <a href="https://pypi.org/project/sqlmesh-hardcharger/"><img src="https://img.shields.io/pepy/dt/sqlmesh-hardcharger.svg" alt="PyPI downloads"></a>
+  <a href="https://github.com/gizmodata/hardcharger-adbc"><img src="https://img.shields.io/badge/driver-Hardcharger%20ADBC-f15a24.svg" alt="Hardcharger ADBC driver"></a>
+  <a href="https://github.com/gizmodata/warp-sql"><img src="https://img.shields.io/badge/protocol-Warp%20SQL-31a8db.svg" alt="Warp SQL protocol"></a>
+  <a href="https://github.com/gizmodata/sqlmesh-hardcharger/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-brightgreen.svg" alt="Apache 2.0 license"></a>
+  <a href="https://gizmodata.com"><img src="https://img.shields.io/badge/by-GizmoData%E2%84%A2-f15a24.svg" alt="GizmoData™"></a>
+</p>
+
+
+Run [SQLMesh](https://sqlmesh.com) transformations on [Hardcharger™](https://gizmodata.com/hardcharger), GizmoData's DuckDB 2.0 server. Connect using the native [Hardcharger ADBC driver](https://github.com/gizmodata/hardcharger-adbc) over **Warp SQL HTTP(S)**.
+
+## Install
+
+```bash
+pip install sqlmesh-hardcharger
+```
+
+Python **3.11 or later**. Installs SQLMesh 0.236.4 (compatible 0.236.x releases) and `adbc-driver-hardcharger>=2.0.2,<3`. SQLGlot stays within SQLMesh's supported 30.8.x range. The local DuckDB package is SQLMesh's dependency; remote queries execute on the Hardcharger server's DuckDB 2.0 engine.
+
+## Quick start
+
+Add `config.yaml` to your SQLMesh project:
+
+```yaml
+gateways:
+  hardcharger:
+    connection:
+      type: hardcharger
+      host: localhost
+      port: 31337
+      username: "{{ env_var('HARDCHARGER_USERNAME') }}"
+      password: "{{ env_var('HARDCHARGER_PASSWORD') }}"
+      use_encryption: true
+      # database: analytics  # optional existing default catalog
+    state_connection:
+      type: duckdb
+      database: sqlmesh_state.duckdb
+
+default_gateway: hardcharger
+model_defaults:
+  dialect: duckdb
+```
+
+Use the included CLI, which registers the adapter **before** SQLMesh loads YAML:
+
+```bash
+sqlmesh-hardcharger info
+sqlmesh-hardcharger plan
+sqlmesh-hardcharger run
+```
+
+It exposes SQLMesh's standard commands and options. For a local server without TLS, explicitly set `use_encryption: false`; otherwise HTTPS and certificate verification are enabled. The adapter builds `hardcharger://host:port` URIs, adding `?tls=false` only for plaintext.
+
+For the standard `sqlmesh` command, import `sqlmesh_hardcharger` in a Python `config.py` before constructing your SQLMesh `Config`. For Python applications:
+
+```python
+import sqlmesh_hardcharger  # registers type: hardcharger
+from sqlmesh import Context
+
+context = Context(paths="path/to/project")
+try:
+    context.plan(auto_apply=True, no_prompts=True)
+finally:
+    context.close()
+```
+
+Use a separate PostgreSQL state connection for production, following [SQLMesh's state connection guidance](https://sqlmesh.readthedocs.io/en/stable/guides/configuration/#state-connection). The local DuckDB state connection above is for development. The tests also exercise state migrations on Hardcharger, but SQLMesh does not recommend this custom engine for production state storage.
+
+## Features
+
+- DuckDB SQL generation, SQLMesh plan/apply/run, incremental models, logical merges, SCD type 2 and table diffs.
+- Arrow-native bulk DataFrame ingestion, including partial source columns, typed nulls and reordered columns.
+- Native ADBC transactions and nested SQLMesh transaction scopes, with rollback on errors.
+- Catalog discovery and switching, automatic schema creation, quoted identifiers and non-default catalogs.
+- DuckLake with PostgreSQL metadata, partitioning and correct cascade behavior, inherited from current SQLMesh.
+- Password, bearer token, browser OAuth/SSO, trusted external identity token and mutual TLS authentication through the native driver.
+
+## Connection options
+
+| Option | Default | Meaning |
+| --- | --- | --- |
+| `host` | `localhost` | Server hostname or IPv6 address |
+| `port` | `31337` | Warp SQL port (1–65535) |
+| `username`, `password` | unset | Password sign-in |
+| `access_token` | unset | Hardcharger bearer token; omit password credentials |
+| `subject_token` | unset | Trusted identity-provider token for token exchange; omit other credentials |
+| `auth_type` | unset (password) | `password`, `external`, `client_certificate` or `mtls` |
+| `use_encryption` | `true` | HTTPS; false explicitly opts into plain HTTP |
+| `disable_certificate_verification` | `false` | Development-only TLS verification bypass |
+| `tls_root_certs` | unset | PEM CA text or file path |
+| `tls_client_cert`, `tls_client_key` | unset | PEM text or paths for mTLS |
+| `tls_server_name` | unset | Certificate hostname / SNI override |
+| `database` | unset | Existing catalog to select on each new connection |
+| `concurrent_tasks` | `4` | Concurrent SQLMesh tasks |
+| `register_comments` | `true` | Register model comments |
+| `pre_ping` | `false` | Check pooled connections before use |
+
+For browser sign-in, set `auth_type: external` and omit username/password/token. For client-certificate sign-in, set `auth_type: client_certificate`, provide the certificate and key, and omit password/token credentials. See the [driver authentication documentation](https://github.com/gizmodata/hardcharger-adbc/tree/main/python).
+
+Catalog creation attaches a DuckDB file on the **server**. Dropping a catalog detaches it; it never deletes a file on the client or deletes the server's database file. Manage server files through your server administration process. Materialized views, managed models, SQLMesh grant synchronization and custom `when_matched` logical merge clauses are not advertised by this adapter.
+
+## Development and testing
+
+```bash
+uv sync --extra dev --frozen
+uv run ruff check .
+uv run mypy sqlmesh_hardcharger
+uv run pytest  # unit tests
+
+# All inherited and Hardcharger-specific integration tests, including DuckLake:
+docker compose -p sqlmesh-hardcharger -f tests/integration/docker/compose.hardcharger.yaml up -d --wait
+POSTGRES_HOST=127.0.0.1 POSTGRES_PORT=55441 uv run pytest -m integration
+
+# Current upstream DuckDB and shared engine tests, over a real Hardcharger server:
+uv run python scripts/test-upstream.py
+```
+
+The `hardcharger` development dependency downloads and verifies the released server binary on first use. Override it with `HARDCHARGER_SERVER_BINARY` when testing another build. A server is required for integration tests: they fail instead of silently skipping if it cannot start.
+
+All 55 tests from [sqlmesh-gizmosql](https://github.com/gizmodata/sqlmesh-gizmosql/tree/0f4c37e91677b10e0a053cabea812de2ab31403a) are retained. The upstream runner pins SQLMesh v0.236.4 at `f6527ffbd8d54d91e26fab7d36c8f4a061bc6451`, uses the installed SQLMesh package, and replaces connection fixtures without changing assertions. Only the two MotherDuck-specific unit tests are deselected; the upstream suite's own unsupported-feature skips remain visible. Bump the pin and dependency range together when adopting a new SQLMesh API series.
+
+CI tests Python 3.11–3.14, runs the upstream compatibility job, checks types and lint, builds the wheel/sdist, and publishes from version tags using PyPI Trusted Publishing with attestations. See [release setup](docs/releasing.md).
+
+## License and origin
+
+Apache-2.0. Adapted from GizmoData's SQLMesh GizmoSQL adapter, preserving its Git history and tests. DuckDB engine semantics are inherited from Apache-2.0 SQLMesh. Hardcharger and GizmoData are trademarks of GizmoData.

sqlmesh_hardcharger-1.0.0/docs/releasing.md

@@ -0,0 +1,28 @@
+# Publishing sqlmesh-hardcharger
+
+## One-time PyPI setup
+
+At https://pypi.org/manage/account/publishing/ add a **pending GitHub publisher**:
+
+| Field | Exact value |
+| --- | --- |
+| PyPI project name | `sqlmesh-hardcharger` |
+| GitHub owner | `gizmodata` |
+| Repository name | `sqlmesh-hardcharger` |
+| Workflow filename | `ci.yml` |
+| Environment name | `release` |
+
+Enter only the workflow filename, not `.github/workflows/ci.yml`. The GitHub `release` environment exists and accepts `v*` tags. No API token secret is needed. A pending publisher creates the PyPI project on the first successful upload; it does not reserve the name beforehand. After the first publication, manage it at https://pypi.org/manage/project/sqlmesh-hardcharger/settings/publishing/.
+
+References: https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/ and https://docs.pypi.org/trusted-publishers/adding-a-publisher/.
+
+## Release
+
+1. Update both package versions (`pyproject.toml` and `sqlmesh_hardcharger/__init__.py`), CHANGELOG and `uv.lock`.
+2. Run CI on `main`, including the complete inherited/regression suite and pinned upstream tests.
+3. Confirm the trusted publisher above is configured.
+4. Tag the validated commit (`v1.0.0` for the first release) and push the tag.
+5. The `ci.yml` workflow reruns tests, builds/checks artifacts, publishes with an OIDC identity and PyPI attestations, then creates the GitHub release.
+6. Verify a fresh PyPI installation and published metadata/provenance. Update the Hardcharger integrations page only after PyPI publication succeeds.
+
+A failed upload can be retried by rerunning the failed job; do not change the tag or attempt to overwrite a published version. Use a new version for changed artifacts.