stackql / stackql/stackql-devel

[FEATURE] Support for outer join semantics

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

Nobody has claimed this yet.

enhancement v0.4
Dominant language
Go
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Feature Description

Outer join semantics are useful in SQL, but do not make sense for parameterisation of HTTP methods. This feature request is for:

  • support of inequality join predicates where they make sense.
  • decent error messaging where they are supplied but disallowed.
  • probably classic case for v1 outer joins is some sort of insert into... t1 LEFT OUTER JOIN t2 on t1.some_col = t2.some_col where t2.some_col is null; motivated by desired or expected absence.

Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

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.

Research direction

No files, tests, or entry points are named. First clarify which SQL join forms and inequality predicates are in scope, how they relate to HTTP method parameterization, and what error behavior and v1 support should be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sql
Domain
api, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.