[coverage] Conformance findings: STATEMENT-023

Open
#885 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python, sql
Domain
databases

Research direction

Start by locating the cursor.rowcount implementation and the STATEMENT-023 conformance test described in the issue; compare the expected behavior with the reference driver PR. The work is done when DDL and SELECT statements report a rowcount of 0 instead of -1 and the corresponding expected-failure test passes.

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-python.

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.

  • STATEMENT-023: cursor.rowcount returns the -1 unknown/NA sentinel for DDL (CREATE TABLE) and SELECT instead of normalizing to 0; it is initialised to -1 and only overwritten when the server reports numModifiedRows, which is None for those statements

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
Python
Stars
233
Forks
152
Avg merge
21h 5m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

First steps

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

More from databricks/databricks-sql-python

All issues in databricks/databricks-sql-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.