pgsql-parser
parser
| pgsql-parser | parser | |
|---|---|---|
| 2 | 3 | |
| 120 | 1,396 | |
| 0.8% | 0.4% | |
| 8.8 | 3.2 | |
| 2 days ago | 5 months ago | |
| PLpgSQL | Go | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pgsql-parser
-
From Postgres Proto to TypeScript – new transpiler for tooling
pgsql-parser: https://github.com/launchql/pgsql-parser
Additionally, we now have new utilities generated by the proto parser, make sure to checkout the @pgsql/utils! That has some cool features in it:
@pgsql/enums: https://github.com/launchql/pgsql-parser/tree/main/packages/...
-
Open Source SQL Parsers
JS: psql-parser in Node and pg-query-emscripten in the browser
parser
-
sqlc: Generating go code from sql statements
For MySQL the situation is a bit different. sqlc uses the parser of TiDB (https://github.com/pingcap/parser), which is a parser that aims to be basically compatible with MySQL, but is quite young and is not a MySQL parser. The most basic queries work, but even simple joins or aggregations usually result in variables with unknown data types or wrong nullability. So you loose a lot of the benefits of sqlc. Manual type annotations for MySQL also do not work most of the time. They are simply ignored and forwarded to MySQL as invalid query if they do not occur on a place where sqlc is expecting them.
-
Wp-SQLite: WordPress running on an SQLite database
This is a disaster waiting to happen. Regular expressions should never be used to parse non-regular languages, of which SQL is one.
There are a variety of mature MySQL dialect parsers available[1][2], and MySQL should have its own public APIs for transforming a query into an AST. Any of those would be a safer and more correct alternative.
[1]: https://github.com/pingcap/parser
[2]: https://github.com/square/mysql-parser
-
Open Source SQL Parsers
Pingcap parser is a MySQL parser in Go.
What are some alternatives?
zetasql - ZetaSQL - Analyzer Framework for SQL
ANTLR - ANTLR (ANother Tool for Language Recognition) is a powerful parser generator for reading, processing, executing, or translating structured text or binary files.
pg_query - Ruby extension to parse, deparse and normalize SQL queries using the PostgreSQL query parser
mo-sql-parsing - Let's make a SQL parser so we can provide a familiar interface to non-sql datastores!
libpg_query - C library for accessing the PostgreSQL parser outside of the server environment
Apache Calcite - Apache Calcite
pg_query_go - Go library to parse and normalize SQL queries using the PostgreSQL query parser
pg-query-emscripten - Emscripten Port of pg_query to easily play with it in the browser
pg_parse - PostgreSQL parser for Rust that uses the actual PostgreSQL server source to parse SQL queries and return the internal PostgreSQL parse tree.
pglast - PostgreSQL Languages AST and statements prettifier: master branch covers PG10, v2 branch covers PG12, v3 covers PG13, v4 covers PG14, v5 covers PG15, v6 covers PG16