I hope this ticket will serve as a place to discuss the current status of the sqlparser-rs project and where the maintainers plan to take it

Background / People with Write Access

This project was initially started by @andygrove

At various times, @benesch @maxcountryman @Dandandan @nickolay and myself have helped maintain the code. This is also the list of people who have write access to the github repo and crates.io https://crates.io/crates/sqlparser

Current Status

The project is structurally complete -- the maintainers accept straightforward additions to support other sql statements and dialects as described in https://github.com/sqlparser-rs/sqlparser-rs#contributing but basically we haven't made any significant changes to the crate in several years.

Issues with Current Status

However, there are proposals to make more more significant improvements to sqlparser, and this is where we run into issues.

Some examples:

• @lovasoa 's proposal to add a visitor in Add an AST visitor #601
• @46bit 's proposal to avoid stack overflows in Prevent stack overflows by limiting recursion #501
• There have also been proposals to make individual Structs vs one big enum

These are all great feature ideas, but they also require downstream code churn as well as additional maintenance. There are different opinions on how the benefit vs cost tradeoff

However, all such ideas basically die in the "the maintainers aren't willing or have time to review / maintain the changes" phase. This mismatch in expectation is not fair to contributors

Possible ways forward

We can add new maintainers to this crate who have more energy (as @lovasoa has offered here: #601 (comment)) that can take the project in a new direction

We work on an "ecosystem" of crates so that additional add on crates can add functionality that is not in the core sqlparser crate

Users who want new features can fork the project (it is all apache 2 licensed and there are no restrictions on doing so)