apache / apache/datafusion-sqlparser-rs

Support of new Syntax

Open
#2,082 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
3.5k
Forks
772
Avg merge
4d 9h
Merged PRs (30d)
17

Description

Hello,

a project of the company I am working for, requires a high performance SQL parser such as this one. However, we would mainly require the [Exasol](https://www.exasol.com/) syntax (which is a lot like Oracle syntax) and we may also need DB2 (z/OS and LUW) syntax.

We are considering and willing to implement the needed syntax and would love to officially contribute that syntax here and share it with the community. But before we start working on it, we have to check our internal policies, whether we are allowed to do so or not. Furthermore, we would like to ask you as well for your opinion on this, since Exasol is not a very popular or widespread RDBMS and the readme specifically states the following:
> The most commonly accepted PRs add support for ... a **popular** RDBMS ... will likely be accepted after a brief review.

We want to make sure, that our contribution would be be accepted and supported (being reviewed) by the responsible contributors of this project (of course only if it meets all the standards and contribution guidelines).

I am looking forward to a hopefully positive reply!

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by reading the README's syntax-support and contribution guidance, then review how dialects are currently represented before discussing Exasol and DB2 scope with maintainers. Done requires an agreed scope and accepted implementation plan, not just a parser change.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, sql
Domain
compilers, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.