[coverage] Conformance findings: DATATYPE-041,STATEMENT-023

Open

#470 opened on Jul 30, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 48/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: sql, typescript
Domain: api, backend, databases

Research direction

Start with the DATATYPE-041 and STATEMENT-023 expected-failure tests in the coverage PR, then compare the behavior with the reference databricks-sql-go PR. Done means the Node.js driver reports STRING for the untyped NULL column and returns the affected-row counts for the 3-row INSERT and 2-row UPDATE through the SEA backend.

Written by the indexing model from the issue text.

Description

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-nodejs.

Each is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT behavior and stays red until this driver is fixed.

DATATYPE-041: SEA backend reports an untyped NULL (VOID) column as TTypeId 16 (NULL) instead of the server-reported STRING type; the same query on Thrift correctly reports STRING, so the column type a caller sees depends on the transport
STATEMENT-023: SEA backend reports no affected-row count for real DML (numModifiedRows absent for a 3-row INSERT and a 2-row UPDATE) while Thrift reports 3 and 2; absent is returned for every statement alike, so a caller cannot distinguish a real modified-row count from "no count available"

Reference driver PR: https://github.com/databricks/databricks-sql-go/pull/416
Coverage PR (reproducing xfail tests): https://github.com/databricks/databricks-driver-test/pull/1010

Dominant language: TypeScript
Stars: 36
Forks: 50
Avg merge: 13h 46m
Merged PRs (30d): 9

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[good first issue] 🍘 Add new Trivia Question 535 (good-first-issue) Open

community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs

Difficulty 1/5 Under an hour Newbie friendliness 95/100

lingdojo/kana-dojo#30695 · 1 comment · 5 reactions · Opened Sep 21, 2026
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Open

category/integration priority/P3 scope/documentation status/ready-for-human type/feature-request

Difficulty 1/5 Under an hour Newbie friendliness 84/100

QwenLM/qwen-code#12428 · 3 comments · Opened Sep 21, 2026
The login flow's text-link submit is 42 px tall on a narrow screen; its docblock says 44 Open

area:auth FE mvp P3

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

klasolsson81/jobbliggaren#1788 · Opened Sep 21, 2026
runner() accepts oneBatchOnly but does not forward it Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

get-convex/migrations#69 · Opened Sep 21, 2026
Savings account view is unreadable in dark mode — the account name and every detail value are hardcoded #2c3e50 (1.52:1) Open

accessibility angular bug good first issue typescript ux

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

apache/fineract-backoffice-ui#584 · 1 comment · Opened Sep 21, 2026

More TypeScript issues