I'm happy to announce sqlparse 0.1.3.
sqlparse is a non-validating SQL parser module.
This is a bug fix release.
Changes since 0.1.2 -------------------
Bug Fixes * Improve parsing of floats (thanks to Kris). * When formatting a statement a space before LIMIT was removed (issue35). * Fix strip_comments flag (issue38, reported by ooberm...@gmail.com). * Avoid parsing names as keywords (issue39, reported by djo...@taket.org). * Make sure identifier lists in subselects are grouped (issue40, reported by djo...@taket.org). * Split statements with IF as functions correctly (issue33 and issue29, reported by charles....@unige.ch). * Relax detection of keywords, esp. when used as function names (issue36, nyuhu...@gmail.com). * Don't treat single characters as keywords (issue32). * Improve parsing of stand-alone comments (issue26). * Detection of placeholders in paramterized queries (issue22, reported by Glyph Lefkowitz). * Add parsing of MS Access column names with braces (issue27, reported by frankz...@gmail.com).
Other * Replace Django by Flask in App Engine frontend (issue11).
Special thanks to Andriy Senkovych for packaging sqlparse for Debian/Ubuntu and giving some insights in all that packaging stuff. Thanks to all other package maintainers too!
What is sqlparse ================
sqlparse is a non-validating SQL parser module for Python. The module provides functions for splitting, formatting and parsing SQL statements. Please file bug reports and feature request on the issue tracker.
Project Page: http://python-sqlparse.googlecode.com Documentation: http://sqlparse.readthedocs.org/ Discussions: http://groups.google.com/group/sqlparse Issues/Bugs: http://code.google.com/p/python-sqlparse/issues/list Online Demo: http://sqlformat.appspot.com