taplo VS sqlparser-rs

You might find useful this: https://github.com/tamasfe/taplo

Some CLI tools have man pages and in such situations like writing completion spec, people usually use them as a source to learn about the tool and its subcommands options, etc. (Usually they have the best reputation for being the most accurate source of information). Though, the tool I chose to write the completion spec, taplo, did not have any manual entry pages. Even better! I found their website and documentation which was really helpful.

Because I targeted WASM, I needed to roll my own. It simply needs async functions as handlers and a world state that is passed along with the requests to the handlers. (example here). You can use it as an example, the code is not the prettiest, but I'll happily answer questions.

sqlparser to parse SQL queries and detect variable bindings

So to start with this, I looked into SQL parsing and found this library https://github.com/sqlparser-rs/sqlparser-rs

We switched to an open source alternative, the rust-based sqlparser-rs library, contributing a few updates for the BigQuery dialect.

I have experience with sqlparser-rs (for my sqlpage project), but it does not track the source code location of the parsed data structures (yet).

It uses https://github.com/sqlparser-rs/sqlparser-rs as the parser and lexer. The binder, planner, optimizer and executor are in Python. The optimizer stage only works on the logical plan and the rules are heuristic only.

That code could be copied directly from some real-world examples - sqlparser-rs code looks pretty much exactly the same.

https://github.com/sqlparser-rs/sqlparser-rs

Also neat to find the SQL parser library they use.