Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[coverage] Conformance findings: METADATA-038

Aberta
  • Algo errado?
#539 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
55/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
node.js, typescript
Domínio
databases

Direção de pesquisa

Start by locating getCrossReference and the SHOW-based foreign-key reshape; the coverage PR diff under tests/ contains the failing test. Compare the reshape with the server-reported updateRule and deleteRule values. Done when reported values are preserved as numeric cells, absent values remain null, and the unrelated-table query returns no rows with the canonical columns.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-nodejs. 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-nodejs) is fixed, then flips green as a tripwire.

Findings

  • METADATA-038 [sea]: SEA getCrossReference drops server-reported referential-action rules: the SHOW FOREIGN KEYS response carries updateRule/deleteRule (both "3" for a declared FK) but the kernel's SHOW-based FK reshape emits hard-coded NULLs for UPDATE_RULE/DELETE_RULE, so a reported value is discarded instead of being narrowed into the nullable Int16 column; thrift surfaces the same rules correctly
    • failing test: getCrossReference — UPDATE_RULE / DELETE_RULE carry the server's rule values (see the coverage PR diff under tests/)

Reproduce & Expected

METADATA-038 — Validates that the FK (cross-reference) result PRESERVES the referential-action rule codes the server reported, in the canonical UPDATE_RULE / DELETE_RULE columns, and emits NULL — never a synthesize…

Reproduce:

  • Phase 1 — call the cross-reference operation for the parent/child FK pair
  • Phase 2 — call it for two unrelated tables (no FK between them)

Expected (per the shared spec):

  • Both phases complete successfully
  • Phase 1 returns at least one FK row
  • Phase 1, the core contract. For every FK row, each rule cell agrees with what the server reported on the FK metadata response observed through the proxy (updateRule / deleteRule on the SHOW-shaped response, UPDATE_RULE / DELETE_RULE on the native metadata response): a reported value is surfaced, and a field that is absent or null is surfaced as NULL. The driver must not substitute a default rule code for an unreported field, and must not drop a reported one. The two columns are asserted independently — one may be reported while the other is not. Do NOT assert the cells are non-null: a server that reports no rules is conforming.
  • Phase 1. Every non-NULL cell is a documented JDBC importedKey* rule code (0..6) — i.e. a narrowed integer, not a truncated or re-interpreted wider value.
  • Phase 1. Same code space as UPDATE_RULE.
  • Phase 1, on surfaces with typed result columns only: the rule columns are a NULLABLE 16-bit integer (JDBC SMALLINT, ODBC SQL_SMALLINT, Arrow Int16). Surfaces that deliver untyped rows (e.g. Node.js plain objects) satisfy this structurally with a numeric-or-null cell.
  • Phase 1 negative control — unchanged by this case. PK_NAME carries the server's PK constraint name or NULL; it is never synthesized and never an empty string.
  • Phase 2 returns zero rows for the unrelated pair (no error).
  • Phase 2. An empty FK result still reports the full canonical cross-reference column set — UPDATE_RULE / DELETE_RULE included — so the rule columns are part of the schema contract, not an artifact of there being rows. Surfaces with their own standardised FK layout (ODBC SQLForeignKeys) assert that layout's canonical column set in its own order.

Context

Linguagem predominante
TypeScript
Estrelas
37
Forks
51
Merge médio
10h 38min
PRs com merge (30d)
8

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de databricks/databricks-sql-nodejs

Todas as issues de databricks/databricks-sql-nodejs

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.