diff options
author | Audrius Kažukauskas <audrius@neutrino.lt> | 2014-05-26 09:16:12 +0700 |
---|---|---|
committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2014-05-28 23:45:35 +0700 |
commit | da8accbc1b557f31c0c7141897a6da324eb89b9e (patch) | |
tree | 0f152636343c065da0f045bc7d90a4178b542555 /system/pgsanity/README | |
parent | 63bf481d1aa244ec7a1928000768f2e2b4ad40ff (diff) | |
download | slackbuilds-da8accbc1b557f31c0c7141897a6da324eb89b9e.tar.gz |
system/pgsanity: Added (SQL syntax checker for PostgreSQL).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/pgsanity/README')
-rw-r--r-- | system/pgsanity/README | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/system/pgsanity/README b/system/pgsanity/README new file mode 100644 index 0000000000..1e83b1a933 --- /dev/null +++ b/system/pgsanity/README @@ -0,0 +1,10 @@ +PgSanity checks the syntax of PostgreSQL SQL files. + +It does this by leveraging the ecpg command which is traditionally used +for preparing C files with embedded SQL for compilation. However, as +part of that preparation, ecpg checks the embedded SQL statements for +syntax errors using the exact same parser that is in PostgreSQL. + +So the approach that PgSanity takes is to take a file that has a list of +bare SQL in it, make that file look like a C file with embedded SQL, run +it through ecpg and let ecpg report on the syntax errors of the SQL. |