pg_parse VS parser

Compare pg_parse vs parser and see what are their differences.

pg_parse

PostgreSQL parser for Rust that uses the actual PostgreSQL server source to parse SQL queries and return the internal PostgreSQL parse tree. (by paupino)

parser

A MySQL Compatible SQL Parser (by pingcap)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
pg_parse parser
1 3
67 1,395
- 1.0%
3.9 3.2
3 months ago 5 months ago
Rust Go
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

pg_parse

Posts with mentions or reviews of pg_parse. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-08.

parser

Posts with mentions or reviews of parser. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-17.
  • sqlc: Generating go code from sql statements
    4 projects | /r/golang | 17 May 2022
    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
    9 projects | news.ycombinator.com | 16 May 2022
    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
    17 projects | dev.to | 8 Oct 2021
    Pingcap parser is a MySQL parser in Go.

What are some alternatives?

When comparing pg_parse and parser you can also consider the following projects:

libpg_query - C library for accessing the PostgreSQL parser outside of the server environment

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_go - Go library to parse 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!

pg_query - Ruby extension to parse, deparse and normalize SQL queries using the PostgreSQL query parser

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

zetasql - ZetaSQL - Analyzer Framework for SQL

pg-query-emscripten - Emscripten Port of pg_query to easily play with it in the browser

Apache Hive - Apache Hive