Parse and examine structure of sql queries
use SQL::Statement;
my $sql = "SELECT a FROM b JOIN c WHERE c=? AND e=7 ORDER BY f DESC LIMIT 5,2";
my $parser = SQL::Parser->new();
$parser->{RaiseError}=1;
$parser->{PrintError}=0;
$parser->parse("LOAD 'MyLib::MySyntax' ");
my $stmt = SQL::Statement->new($sql,$parser);
printf "Command %s\n",$stmt->command;
printf "Num of Placeholders %s\n",scalar $stmt->params;
printf "Columns %s\n",join( ',', map {$_->name} $stmt->column_defs() );
printf "Tables %s\n",join( ',', map {$_->name} $stmt->tables() );
printf "Where operator %s\n",join( ',', $stmt->where->op() );
printf "Limit %s\n",$stmt->limit();
printf "Offset %s\n",$stmt->offset();
# these will work not before $stmt->execute()
printf "Order Columns %s\n",join(',', map {$_->column} $stmt->order() );
The SQL::Statement module can be used by itself, without \s-1DBI\s0 and without a subclass to parse \s-1SQL\s0 statements and to allow you to examine the structure of the statement (table names, column names, where clause predicates, etc.). It will also execute statements using in-memory tables. That means that you can create and populate some tables, then query them and fetch the results of the queries as well as examine the differences between statement metadata during different phases of prepare, execute, fetch. See the remainder of this document for a description of how to create and modify a parser object and how to use it to parse and examine \s-1SQL\s0 statements. See SQL::Statement for other uses of the module.
The parser object only needs to be created once per script. It can then be reused to parse any number of \s-1SQL\s0 statements. The basic creation of a parser is this:
my $parser = SQL::Parser->new();
You can set the error-reporting for the parser the same way you do in \s-1DBI:\s0
$parser->{RaiseError}=1; # turn on die-on-error behaviour $parser->{PrinteError}=1; # turn on warnings-on-error behaviour
As with \s-1DBI\s0, RaiseError defaults to 0 (off) and PrintError defaults to 1 (on).
For many purposes, the built-in \s-1SQL\s0 syntax should be sufficient. However, if you need to, you can change the behaviour of the parser by extending the supported \s-1SQL\s0 syntax either by loading a file containing definitions; or by issuing \s-1SQL\s0 commands that modify the way the parser treats types, keywords, functions, and operators.
$parser->parse("LOAD MyLib::MySyntax"); $parser->parse("CREATE TYPE myDataType");
See SQL::Statement::Syntax for details of the supported \s-1SQL\s0 syntax and for methods of extending the syntax.
While you only need to define a new SQL::Parser object once per script, you need to define a new SQL::Statment object once for each statement you want to parse.
my $stmt = SQL::Statement->new($sql, $parser);
The call to new() takes two arguments - the \s-1SQL\s0 string you want to parse, and the SQL::Parser object you previously created. The call to new is the equivalent of a \s-1DBI\s0 call to prepare() - it parses the \s-1SQL\s0 into a structure but does not attempt to execute the \s-1SQL\s0 unless you explicitly call execute().
The following methods can be used to obtain information about a query:
Returns the \s-1SQL\s0 command. See SQL::Statement::Syntax for supported command. Example:
my $command = $stmt->command();
my $numColumns = $stmt->column_defs(); # Scalar context my @columnList = $stmt->column_defs(); # Array context my($col1, $col2) = ($stmt->column_defs(0), $stmt->column_defs(1));
This method is used to retrieve column lists. The meaning depends on the query command:
SELECT $col1, $col2, ... $colN FROM $table WHERE ... UPDATE $table SET $col1 = $val1, $col2 = $val2, ... $colN = $valN WHERE ... INSERT INTO $table ($col1, $col2, ..., $colN) VALUES (...)
When used without arguments, the method returns a list of the columns $col1, $col2, ..., $colN, you may alternatively use a column number as argument. Note that the column list may be empty as in
INSERT INTO $table VALUES (...)
and in \s-1CREATE\s0 or \s-1DROP\s0 statements.
But what does \*(L"returning a column\*(R" mean? It is returning an \*(C`SQL::Statement::Util::Column\*(C' instance, a class that implements the methods \*(C`table\*(C' and \*(C`name\*(C', both returning the respective scalar. For example, consider the following statements:
INSERT INTO foo (bar) VALUES (1) SELECT bar FROM foo WHERE ... SELECT foo.bar FROM foo WHERE ...
In all these cases exactly one column instance would be returned with
$col->name() eq 'bar' $col->table() eq 'foo'
my $tableNum = $stmt->tables(); # Scalar context my @tables = $stmt->tables(); # Array context my($table1, $table2) = ($stmt->tables(0), $stmt->tables(1));
Similar to \*(C`columns\*(C', this method returns instances of \*(C`SQL::Statement::Table\*(C'. For \s-1UPDATE\s0, \s-1DELETE\s0, \s-1INSERT\s0, \s-1CREATE\s0 and \s-1DROP\s0, a single table will always be returned. \s-1SELECT\s0 statements can return more than one table, in case of joins. Table objects offer a single method, \*(C`name\*(C' which returns the table name.
my $paramNum = $stmt->params(); # Scalar context my @params = $stmt->params(); # Array context my($p1, $p2) = ($stmt->params(0), $stmt->params(1));
The \*(C`params\*(C' method returns information about the input parameters used in a statement. For example, consider the following:
INSERT INTO foo VALUES (?, ?)
This would return two instances of \*(C`SQL::Statement::Param\*(C'. Param objects implement a single method, \*(C`$param-\*(C'num()>, which retrieves the parameter number. (0 and 1, in the above example). As of now, not very useful ... :-)
my $rowValueNum = $stmt->row_values(); # Scalar context my @rowValues = $stmt->row_values(0); # Array context my($rval1, $rval2) = ($stmt->row_values(0,0), $stmt->row_values(0,1));
This method is used for statements like
UPDATE $table SET $col1 = $val1, $col2 = $val2, ... $colN = $valN WHERE ... INSERT INTO $table (...) VALUES ($val1, $val2, ..., $valN), ($val1, $val2, ..., $valN)
to read the values $val1, $val2, ... $valN. It returns (lists of) scalar values or \*(C`SQL::Statement::Param\*(C' instances.
my $orderNum = $stmt->order(); # Scalar context my @order = $stmt->order(); # Array context my($o1, $o2) = ($stmt->order(0), $stmt->order(1));
In \s-1SELECT\s0 statements you can use this for looking at the \s-1ORDER\s0 clause. Example:
SELECT * FROM FOO ORDER BY id DESC, name
In this case, \*(C`order\*(C' could return 2 instances of \*(C`SQL::Statement::Order\*(C'. You can use the methods \*(C`$o->table()\*(C', \*(C`$o->column()\*(C', \*(C`$o->direction()\*(C' and \*(C`$o->desc()\*(C' to examine the order object.
my $limit = $stmt->limit();
In a \s-1SELECT\s0 statement you can use a \*(C`LIMIT\*(C' clause to implement cursoring:
SELECT * FROM FOO LIMIT 5 SELECT * FROM FOO LIMIT 5, 5 SELECT * FROM FOO LIMIT 10, 5
These three statements would retrieve the rows 0..4, 5..9, 10..14 of the table \s-1FOO\s0, respectively. If no \*(C`LIMIT\*(C' clause is used, then the method \*(C`$stmt->limit\*(C' returns undef. Otherwise it returns the limit number (the maximum number of rows) from the statement (5 or 10 for the statements above).
my $offset = $stmt->offset();
If no \*(C`LIMIT\*(C' clause is used, then the method \*(C`$stmt->limit\*(C' returns undef. Otherwise it returns the offset number (the index of the first row to be included in the limit clause).
my $where_hash = $stmt->where_hash();
To manually evaluate the \s-1WHERE\s0 clause, fetch the topmost where clause node with the \*(C`where_hash\*(C' method. Then evaluate the left-hand and right-hand side of the operation, perhaps recursively. Once that is done, apply the operator and finally negate the result, if required.
The where clause nodes have (up to) 4 attributes:
contains the operator, one of \*(C`AND\*(C', \*(C`OR\*(C', \*(C`=\*(C', \*(C`<>\*(C', \*(C`>=\*(C', \*(C`>\*(C', \*(C`<=\*(C', \*(C`<\*(C', \*(C`LIKE\*(C', \*(C`CLIKE\*(C', \*(C`IS\*(C', \*(C`IN\*(C', \*(C`BETWEEN\*(C' or a user defined operator, if any.
contains the left-hand side of the operator. This can be a scalar value, a hash containing column or function definition, a parameter definition (hash has attribute \*(C`type\*(C' defined) or another operation (hash has attribute \*(C`op\*(C' defined).
contains the right-hand side of the operator. This can be a scalar value, a hash containing column or function definition, a parameter definition (hash has attribute \*(C`type\*(C' defined) or another operation (hash has attribute \*(C`op\*(C' defined).
contains a \s-1TRUE\s0 value, if the operation result must be negated after evalution.
To illustrate the above, consider the following \s-1WHERE\s0 clause:
WHERE NOT (id > 2 AND name = 'joe') OR name IS NULL
We can represent this clause by the following tree:
(id > 2) (name = 'joe') \ / NOT AND \ (name IS NULL) \ / OR
Thus the \s-1WHERE\s0 clause would return an SQL::Statement::Op instance with the op() field set to '\s-1OR\s0'. The arg2() field would return another SQL::Statement::Op instance with arg1() being the SQL::Statement::Column instance representing id, the arg2() field containing the value undef (\s-1NULL\s0) and the op() field being '\s-1IS\s0'.
The arg1() field of the topmost Op instance would return an Op instance with op() eq '\s-1AND\s0' and neg() returning \s-1TRUE\s0. The arg1() and arg2() fields would be Op's representing \*(L"id > 2\*(R" and \*(L"name = 'joe'\*(R".
Of course there's a ready-for-use method for \s-1WHERE\s0 clause evaluation:
The \s-1WHERE\s0 clause evaluation depends on an object being used for fetching parameter and column values. Usually this can be an SQL::Statement::RAM::Table object or SQL::Eval object, but in fact it can be any object that supplies the methods
$val = $eval->param($paramNum); $val = $eval->column($table, $column);
Once you have such an object, you can call eval_where;
$match = $stmt->eval_where($eval);
my $where = $stmt->where();
This method is used to examine the syntax tree of the \*(C`WHERE\*(C' clause. It returns undef (if no \*(C`WHERE\*(C' clause was used) or an instance of SQL::Statement::Term.
The where clause is evaluated automatically on the current selected row of the table currently worked on when it's \*(C`value()\*(C' method is invoked.
\*(C`SQL::Statement\*(C' creates the object tree for where clause evaluation directly after successfully parsing a statement from the given \*(C`where_clause\*(C', if any.
When called from a \s-1DBD\s0 or other subclass of SQL::Statement, the execute() method will be executed against whatever datasource (persistent storage) is supplied by the \s-1DBD\s0 or the subclass (e.g. \s-1CSV\s0 files for \s-1DBD::CSV\s0, or BerkeleyDB for \s-1DBD::DBM\s0). If you are using SQL::Statement directly rather than as a subclass, you can call the execute() method and the statements will be executed() using temporary in-memory tables. When used directly, like that, you need to create a cache hashref and pass it as the first argument to execute:
my $cache = {}; my $parser = SQL::Parser->new(); my $stmt = SQL::Statement->new('CREATE TABLE x (id INT)',$parser); $stmt->execute( $cache );
If you are using a statement with placeholders, those can be passed to execute after the $cache:
$stmt = SQL::Statement->new('INSERT INTO y VALUES(?,?)',$parser); $stmt->execute( $cache, 7, 'foo' );
Only a single \*(C`fetch()\*(C' method is provided - it returns a single row of data as an arrayref. Use a loop to fetch all rows:
while (my $row = $stmt->fetch()) { # ... }
#!/usr/bin/perl -w use strict; use SQL::Statement;
my $cache={}; my $parser = SQL::Parser->new(); for my $sql(split /\n/, " CREATE TABLE a (b INT) INSERT INTO a VALUES(1) INSERT INTO a VALUES(2) SELECT MAX(b) FROM a " ) { $stmt = SQL::Statement->new($sql,$parser); $stmt->execute($cache); next unless $stmt->command eq 'SELECT'; while (my $row=$stmt->fetch) { print "@$row\n"; } } _\|_END_\|_
Copyright (c) 2005, Jeff Zucker <jzuckerATcpan.org>, all rights reserved. Copyright (c) 2009, Jens Rehsack <rehsackATcpan.org>, all rights reserved.
This document may be freely modified and distributed under the same terms as Perl itself.