by forward

forward /sql-parser

A SQL parser written in pure JS

452 Stars 119 Forks Last release: Not found MIT License 61 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

SQL Parser

SQL Parser is a lexer, grammar and parser for SQL written in JS. Currently it is only capable of parsing fairly basic SELECT queries but full SQL support will hopefully come in time. See the specs for examples of currently supported queries.


The package is distributed on NPM and can be installed with...

npm install sql-parser

To build from source you'll need to run the following from the root of the project...

npm install
cake build

Tests are written using Mocha and can be run with...

npm test


The lexer takes a SQL query string as input and returns a stream of tokens in the format

['NAME', 'value', lineNumber]

Here is a simple example...

lexer.tokenize('select * from my_table')

[ ['SELECT','select',1], ['STAR','*',1], ['FROM','from',1], ['LITERAL','my_table',1] ]

The tokenized output is in a format compatible with JISON.


The parser only currently supports SELECT queries but is able to produce a Select object with properties for where, group, order, limit. See lib/nodes.coffee for more info of the returned object structure. Calling .toString() on a Select object should give you back a well formatted version of the original SQL input.

tokens = lexer.tokenize('select * from my_table where foo = 'bar')

SELECT * FROM my_table WHERE foo = 'bar'


A lot of the boilerplate and compilation code in this project is borrowed from the CoffeeScript project as it was the best example of a project using JISON that I could find. Thanks.


Contributions in the form of pull requests that add syntax support are very welcome but should be supported by both Lexer and Parser level tests.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.