PostgreSQL SQL Parser

The built-in PostgreSQL SQL engine in General SQL Parser provides in-depth analysis of an organization's PostgreSQL SQL script at a detailed level that would not be possible without a complete, 100% compatible query parser.

Parsing SQL is a notoriously difficult task because the SQL syntax of PostgreSQL is very ambiguous in a lot of places. Many people have attempted to write a full SQL grammar with parser generate tool and failed.

Now you can fully incorporated this PostgreSQL SQL parser into your products, instantly adding a powerful SQL processing capability to your program. With the right library, you can get your job done quickly by saving hundred of hours, if not more, on developing time.

Clean up messy SQL codes

Easily integrate SQL formatter into your application for a color coded layout that is easy to navigate, giving your product a professional feeling.

Detect SQL syntax errors

Your application will be able to validate SQL syntax before a database executes the query. This is very useful especially if your SQL was dynamically built based on user input.

Rid SQL injections

Avoid being vulnerable to SQL injection in your ASP.NET or Java application, by automatically detecting malicious SQL segment with our ready-to-use library.

Retrieve/Refactor table & column name

Precisely determining and renaming every table and column in stored SQL statements is very complex with a lot of nesting and sub-queries. With us, however, that tedious procedure can become hassle-free one for you.

Find affected SQL objects

Parse out the affect SQL objects in a SQL file that can have many different types of SQL (select, insert, create, drop, etc), and helping to determine what is being affected, including but not limited to schema, table, column.

Discover the relationship in DDL

Quickly locate the primary key and/or foreign key in DDL scripts to figure out the complex relationship among the various tables. Extracted table, attribute names, data types can be used to generate the CRUD-Statements.

Query parse tree in XML

Parsing SQL is a notoriously difficult task, but we are here to help. You will be provided with a SQL query parse tree in XML output that will allow you to further process SQL scripts.

Rewrite and convert SQL

Modify SQL expression/condition in where clause to reconstruct a new filter. Rewrite Oracle proprietary joins to ANSI SQL compliant joins. Translate SQL between different databases.

CRUD Reportor

Read complex and large SQL scripts to find out tables have Create, Read, Update, Delete and Insert operations against them immediately, it's almost impossible to do that without help with a tool.

SQL Parser can even do more

We are dedicated to constantly improving our product so it will be easier to use with more flexibility, making it a valuable asset to your software product. Here, we have provided you with additional demos that may be helpful to you.


Supported SQL

Level 1: SQL parser recognizes that this is a valid SQL statement, but can't validate the syntax of this specific SQL statement. This demo shows how General SQL Parser can handle this kind of SQL statements.

Level 2: SQL Parser fully parses this kind of SQL statements with detailed query parse tree node elements and provides everything you need to analyze and manipulate this kind of SQL statements.

Level 1 statements: 150, Level 2 statements: 14, generated by General SQL Parser Java Version,2017/09/29

SQL statements Level 1 Level 2
abort Y
alter aggregate Y
alter collation Y
alter conversion Y
alter database Y
alter default privileges Y
alter domain Y
alter event trigger Y
alter extension Y
alter foreign data wrapper Y
alter foreign Table Y
alter function Y
alter group Y
alter index Y
alter language Y
alter large object Y
alter materialized view Y
alter operator Y
alter operator class Y
alter operator family Y
alter role Y
alter schema Y
alter sequence Y
alter server Y
alter table Y Y
alter tablespace Y
alter text search configuration Y
alter text search dictionary Y
alter text search parser Y
alter text search template Y
alter trigger Y
alter type Y
alter user Y
alter user mapping Y
alter view Y
analyze Y
begin Y
checkpoint Y
close Y
cluster Y
comment Y
commit Y
commit prepared Y
copy Y
create aggregate Y
create cast Y
create collation Y
create constraint trigger Y Y
create conversion Y
create database Y
create domain Y
create event trigger Y
create extension Y
create foreign data wrapper Y
create foreign table Y
create function Y Y
create global temp table Y Y
create group Y
create index Y Y
create language Y
create materialized view Y
create operator Y
create operator class Y
create operator family Y
create or replace role Y
create or replace temp view Y Y
create role Y
create schema Y
create sequence Y
create server Y
create tablespace Y
create text search configuration Y
create text search dictionary Y
create text search parser Y
create text search template Y
create type Y
create user Y
create user mapping Y
deallocate Y
declare Y
delete Y Y
discard Y
do Y
drop aggregate Y
drop cast Y
drop collation Y
drop conversion Y
drop database Y
drop domain Y
drop extension Y
drop foreign data wrapper Y
drop foreign table Y
drop function Y
drop group Y
drop index Y
drop language Y
drop materialized view Y
drop operator Y
drop operator class Y
drop operator family Y
drop owned Y
drop role Y
drop rule Y
drop schema Y
drop sequence Y
drop server Y
drop table Y Y
drop tablespace Y
drop text search configuration Y
drop text search dictionary Y
drop text search parser Y
drop text search template Y
drop trigger Y
drop type Y
drop user Y
drop user mapping Y
drop view Y
end Y
execute Y Y
explain Y
fetch Y
grant Y
insert Y Y
listen Y
load Y
lock Y
move Y Y
notify Y
prepare Y
prepare transaction Y
reassign owned Y
refresh materialized view Y
reindex Y
release Y
reset Y
revoke Y
rollback Y
rollback prepared Y
savepoint Y
security label Y
select Y Y
set Y
set constraints Y
set local role Y
set local session authorization Y
set session characteristics as transaction Y
truncate Y Y
unlisten Y
update Y Y
values Y


Any other benefits can I get by using this SQL Parser?

Yes, of course. We collect all kinds of examples in this page to illustrate how and why you want to use general sql parser, hope it can help you to make better use of this library.



If you have any questions about General SQL Parser, You can always send us an email and we'll get back to you within 24 hours.