Top Level :: Database

Package Information: SQL_Parser

Show All Changelogs
» Version » Information
0.5Download

Release date: 2004-05-11 05:08 UTC
Release state: devel

Changelog:

Parser:
* More robust search clause parsing; now handles subsearches
with parentheses in more cases (Brent Cook
* Add more alias handling cases (John Griffin)
* Handle ordinal functions in select project clauses correctly
* Add explicit join support (John Griffin)
* Add initial support for multiple SQL dialects (ANSI, MySQL)
(John Griffin, Brent Cook)
* Added SQL Compiler that takes a parse tree and generates a
SQL statement (John Griffin)

0.4Download

Release date: 2003-12-21 02:54 UTC
Release state: devel

Changelog:

Lexer:
Fixed off-by-one error and other accesses of undefined memory
Idents can be of the form aaa.bbb
Parser:
Can now parse table.field style field names
Understand some forms of table alias
Fix some bugs in error carret display
Fix some references to undefined memory
Handle some subselects
Handle 'in' and 'not in' keywords for sets and subselects
Use new features of Lexer
Fix quantum comparisons in creates
add support for 'group by'
Thanks to John Griffin for many of these fixes. There are many more
left to merge in the next release - hopefully, it wont be too far
in the future.

0.3Download

Release date: 2003-04-14 07:51 UTC
Release state: devel

Changelog:

This is an 'I'm back' release. Did you miss me?

Mostly focusing on the Lexer this time.
* Add support for pushing tokens back (Jason Pell)
* Add support for # and -- comments (for real this time)
* Add support for ellipsis tokens
* Removed extraneous negative-number parsing

0.2Download

Release date: 2002-12-18 11:45 UTC
Release state: devel

Changelog:

* Add support for column and table aliases (thanks to Lauren Matheson)
* Add support for null as a value type (thanks to Jason Pell)

0.1Download

Release date: 2002-09-30 07:55 UTC
Release state: devel

Changelog:

Initial release as a stand-alone package. Lots of documentation is needed (e.g. grammar notes), but it is already pretty robust and easy to extend. The lexer could use some optimization for speed too.