duckhaven-cli 0.3.0__tar.gz → 0.4.0__tar.gz

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/CHANGELOG.md

@@ -6,6 +6,17 @@ All notable changes to `duckhaven-cli` are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-10-15
+
+### Changed
+
+- `dh sql` and the REPL ask the server to hold the submit for up to two seconds, so a quick
+  query finishes in one request instead of a submit and a poll. `--no-wait` still returns at
+  once. A server that predates the hold ignores it.
+- Ready for DuckHaven `api_version` 3: `DECIMAL` and wide integers, which it sends as
+  strings, print as before in table and CSV output and stay exact strings with
+  `--format json`.
+
 ## [0.3.0] - 2026-10-13
 
 Brings the CLI up to date with the DuckHaven server's result cache, DuckLake catalogs,

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: duckhaven-cli
-Version: 0.3.0
+Version: 0.4.0
 Summary: dh — the command-line interface for DuckHaven
 Project-URL: Homepage, https://github.com/tamasmrtn/duckhaven-clients
 Project-URL: Source, https://github.com/tamasmrtn/duckhaven-clients
@@ -77,6 +77,14 @@ maintenance recommendations (`dh admin maintenance recommendations|apply`), and
 private editor tabs (`dh worksheet`). Against an older server these commands answer with the
 server's own not-found or validation error.
 
+## Exact numbers
+
+A DuckHaven with `api_version` 3 or later sends `DECIMAL` values and 64-bit-or-wider integers
+(`BIGINT`, `HUGEINT`, `count(*)`) as strings, because JSON numbers lose precision past about
+16 digits. `dh` prints them exactly as before in table and CSV output. With `--format json`
+they stay strings (`"12.50"`, `"9007199254740993"`), exact. Scripts reading `dh` JSON should
+convert those columns themselves rather than expect JSON numbers.
+
 ## Documentation
 
 - [Command-line quickstart](https://tamasmrtn.github.io/duckhaven/getting-started/cli-quickstart/) — install, sign in,

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/README.md

@@ -48,6 +48,14 @@ maintenance recommendations (`dh admin maintenance recommendations|apply`), and
 private editor tabs (`dh worksheet`). Against an older server these commands answer with the
 server's own not-found or validation error.
 
+## Exact numbers
+
+A DuckHaven with `api_version` 3 or later sends `DECIMAL` values and 64-bit-or-wider integers
+(`BIGINT`, `HUGEINT`, `count(*)`) as strings, because JSON numbers lose precision past about
+16 digits. `dh` prints them exactly as before in table and CSV output. With `--format json`
+they stay strings (`"12.50"`, `"9007199254740993"`), exact. Scripts reading `dh` JSON should
+convert those columns themselves rather than expect JSON numbers.
+
 ## Documentation
 
 - [Command-line quickstart](https://tamasmrtn.github.io/duckhaven/getting-started/cli-quickstart/) — install, sign in,

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/src/dh/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.3.0'
-__version_tuple__ = version_tuple = (0, 3, 0)
+__version__ = version = '0.4.0'
+__version_tuple__ = version_tuple = (0, 4, 0)
 
 __commit_id__ = commit_id = None

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/src/dh/commands/query.py

@@ -64,6 +64,7 @@ def _run(
             # Two timeouts would be a contract people get wrong; one cannot drift.
             timeout_s=budget,
             use_cache=False if no_cache else None,
+            hold=not no_wait,
         )
         if no_wait:
             cli.note(f"Submitted {submitted['id']}.")

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/src/dh/execute.py

@@ -1,7 +1,8 @@
 """One-shot query execution: submit, wait, fetch.
 
-`POST /workspaces/{workspace}/queries` answers **202** with a query that has not
-run yet, so every caller has to poll. This is that loop, done once and correctly.
+`POST /workspaces/{workspace}/queries` holds the call briefly for the run to finish
+and otherwise answers **202** with a query still running, which the caller polls.
+This is that loop, done once and correctly.
 
 It is deliberately not the connector's code path. `duckhaven-sql-connector`
 speaks the *session* API (`connect()` opens one), and sessions are disabled by
@@ -34,6 +35,11 @@ _MAX_DELAY = 2.0
 #: above still paces the loop. Well under the client's socket timeout.
 _HOLD_S = 5.0
 
+#: How long the submit itself asks the server to hold for a finish. Shorter than
+#: `_HOLD_S`: until the submit answers, the query's id is unknown, so a Ctrl-C in
+#: this window cannot cancel the query the way one during polling does.
+_SUBMIT_HOLD_S = 2.0
+
 #: The server caps `limit` here; asking for more is rejected, not truncated.
 _MAX_PAGE = 1000
 
@@ -62,13 +68,20 @@ def submit(
     timeout_s: float | None = None,
     saved_query_id: str | None = None,
     use_cache: bool | None = None,
+    hold: bool = True,
 ) -> dict[str, Any]:
     """Hand the SQL to the server. Returns the accepted query.
 
-    Usually not run yet; a read the result cache can answer comes back already
-    `done`. `use_cache=False` always executes it.
+    Already `done` when it finished within the hold or was answered from the result
+    cache; otherwise still running, for `wait` to follow. `use_cache=False` always
+    executes it. `hold=False` answers at once, for a caller that will not wait.
     """
     body: dict[str, Any] = {"sql": sql}
+    if hold:
+        # A query that finishes inside the hold comes back done on this call, with
+        # nothing to poll. A server too old to know the field ignores it and
+        # answers 202 at once, as before.
+        body["wait_timeout_s"] = _SUBMIT_HOLD_S
     if agent:
         body["agent_id"] = agent
     if catalog:

{duckhaven_cli-0.3.0 → duckhaven_cli-0.4.0}/src/dh/repl.py

@@ -144,7 +144,7 @@ def _run_one_shot(cli, settings, sql: str, agent: str | None) -> None:
             agent=chosen,
             catalog=settings.get("catalog"),
         )
-        finished = execute.wait(client, submitted["id"], timeout=1200)
+        finished = execute.wait(client, submitted["id"], timeout=1200, known=submitted)
         execute.raise_for_status(finished)
         page = execute.fetch_rows(client, finished["id"])
     cli.emit({"columns": page["columns"], "rows": page["rows"], "total": page["total"]})