stackql / stackql/stackql-devel
[FEATURE] Support for outer join semantics
Nobody has claimed this yet.
- 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 joinsis some sort ofinsert 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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