Skip to content

Help wanted: send failing SQL #19

Description

@devops-den

Found a stored procedure where SPXray reports the wrong tables, wrong columns, a missing table, or an invented column? That's exactly the kind of bug report that improves this tool the most.

How to submit:

  1. Reduce your SQL to the smallest snippet that still reproduces the wrong output — no need to send a whole procedure.
  2. Rewrite every real identifier as fictional before pasting it here: schema/table/column names, no real company, client, or vendor names. Same rule as everywhere else in this repo — see tests/fixtures/README.md. A renamed structure is fine; a real schema is not.
  3. Say what SPXray reported vs. what you expected.

What happens to it

Every genuine miss becomes a permanent fixture: it's added under tests/fixtures/, pinned with either a golden snapshot (once fixed) or a strict-xfail known-limitation test (if not fixed yet — see tests/test_known_limitations.py), and it stays in the regression suite forever. This is literally how the recently-fixed KL-12/13/14 (MERGE alias handling, INSERT/DELETE column resolution) were found — real SQL shapes catch things hand-written edge cases don't.

No fix required to contribute — a good failing example is a complete, valuable contribution on its own.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions