[coverage] Conformance findings: CONNPROP-003

[peco-engineer-bot]

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-go. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-sql-go) is fixed, then flips green as a tripwire.

Findings

• CONNPROP-003 [thrift]: Unrecognized DSN connection properties are forwarded to the server as session configuration instead of being dropped, so a DSN with any unknown key fails with CONFIG_NOT_AVAILABLE (SQLSTATE 42K0I) rather than connecting
  • failing test: TestUnrecognizedConnectionPropertyIsTolerated (see the coverage PR diff under tests/)
• CONNPROP-003: Unrecognized DSN connection properties are forwarded to the server as session configuration instead of being dropped, so a DSN carrying any unknown key fails with CONFIG_NOT_AVAILABLE (SQLSTATE 42K0I) rather than connecting

Reproduce & Expected

CONNPROP-003 — Verify that a connection property the driver does not recognize is tolerated: the connection still succeeds, exactly one session is opened, and a query returns results.

Reproduce:

SELECT 1 AS test_value

Expected (per the shared spec):

• completes without an exception
• result has exactly 1 row(s)
• [thrift] exactly 1 OpenSession call(s)
• [sea] exactly 1 CreateSession call(s)

Context

• The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-odbc/pull/178 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-go; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
• Coverage PR carrying the reproducing xfail test(s): https://github.com/databricks/databricks-driver-test/pull/1105