[general]
name=Hardcharger
about=Browse spatial tables and custom SQL from a Hardcharger server directly in QGIS 4.<br/>
    Streams Arrow record batches over the Chargewire protocol (HTTP or HTTPS), with password or browser OAuth/SSO sign-in.
    Credentials are stored encrypted by QGIS Auth Manager. Restart QGIS after upgrading.
category=Database
description=Connect QGIS 4 to Hardcharger and visualize remote spatial data over the Chargewire protocol (HTTP or HTTPS).
hasProcessingProvider=False
icon=resources/images/logo_hardcharger.webp
server=True
tags=hardcharger,database,spatial,sql,arrow,chargewire,duckdb,adbc
author=GizmoData (Philip Moore). Based on qgizmosql and QDuckDB by Oslandia (Florent Fougeres, Jean Felder, Julien Moura).
email=philip@gizmodata.com
homepage=https://github.com/gizmodata/qhardcharger
repository=https://github.com/gizmodata/qhardcharger
tracker=https://github.com/gizmodata/qhardcharger/issues
deprecated=False
experimental=False
qgisMinimumVersion=4.2.3
qgisMaximumVersion=4.99
version=1.1.3
changelog=
    1.1.3 - Hardcharger ADBC 2.4.8 (with ADBC Driver Manager 1.13.0 and PyArrow 26.0.1): the driver library exports only its ADBC entry points, its macOS wheel states the macOS 13 it needs, and errors use the ADBC statuses the conformance suite expects. Tested against Hardcharger 2.7.0.
    1.1.2 - Hardcharger ADBC 2.4.0: after a lost session, a statement is never run again inside a lost SQL transaction or without the session's USE and settings; GizmoData Cloud hosts default to port 443. Tested against Hardcharger 2.7.0.
    1.1.1 - Hardcharger ADBC 2.3.0: a session that replaces a lost one keeps the connection's settings and tags. Tested against Hardcharger 2.7.0.
    1.1.0 - Chargewire protocol naming throughout; Hardcharger ADBC 2.1.0. Still works with Hardcharger servers released before the rename.
    1.0.0 - Stable Hardcharger plugin for QGIS 4 / Qt 6. Native Chargewire HTTP(S), ADBC 2.0.2, PyArrow 26, spatial tables, custom SQL, encrypted credentials, and Arrow streaming.
