Inserting and Updating Arrays

    my $sql = SQL::Abstract->new(array_datatypes => 1);
    my %data = (
        planets => [qw/Mercury Venus Earth Mars/]
    );

    my($stmt, @bind) = $sql->insert('solar_system', \%data);

This results in:

    $stmt = "INSERT INTO solar_system (planets) VALUES (?)"

    @bind = (['Mercury', 'Venus', 'Earth', 'Mars']);

Inserting and Updating SQL

    my %data = (
        name => 'Bill',
        date_entered => \[ "to_date(?,'MM/DD/YYYY')", "03/02/2003" ],
    );

The first value in the array is the actual SQL. Any other values are optional and would be included in the bind values array. This gives you:

    my($stmt, @bind) = $sql->insert('people', \%data);

    $stmt = "INSERT INTO people (name, date_entered)
                VALUES (?, to_date(?,'MM/DD/YYYY'))";
    @bind = ('Bill', '03/02/2003');

An UPDATE is just as easy, all you change is the name of the function:

    my($stmt, @bind) = $sql->update('people', \%data);

Notice that your %data isn't touched; the module will generate the appropriately quirky SQL for you automatically. Usually you'll want to specify a WHERE clause for your UPDATE, though, which is where handling %where hashes comes in handy...

Complex where statements

    my %where = (
       requestor => 'inna',
       worker => ['nwiger', 'rcwe', 'sfz'],
       status => { '!=', 'completed' }
    );

    my($stmt, @bind) = $sql->select('tickets', '*', \%where);

The above would give you something like this:

    $stmt = "SELECT * FROM tickets WHERE
                ( requestor = ? ) AND ( status != ? )
                AND ( worker = ? OR worker = ? OR worker = ? )";
    @bind = ('inna', 'completed', 'nwiger', 'rcwe', 'sfz');

Which you could then use in DBI code like so:

    my $sth = $dbh->prepare($stmt);
    $sth->execute(@bind);

Easy, eh?

new(option => 'value')

case

If set to 'lower', then SQL will be generated in all lowercase. By default SQL is generated in "textbook" case meaning something like:

    SELECT a_field FROM a_table WHERE some_field LIKE '%someval%'
    

Any setting other than 'lower' is ignored.

cmp

This determines what the default comparison operator is. By default it is "=", meaning that a hash like this:

    %where = (name => 'nwiger', email => 'nate@wiger.org');
    

Will generate SQL like this:

    WHERE name = 'nwiger' AND email = 'nate@wiger.org'
    

However, you may want loose comparisons by default, so if you set "cmp" to "like" you would get SQL such as:

    WHERE name like 'nwiger' AND email like 'nate@wiger.org'
    

You can also override the comparison on an individual basis - see the huge section on "WHERE CLAUSES" at the bottom.

sqltrue, sqlfalse

Expressions for inserting boolean values within SQL statements. By default these are "1=1" and "1=0". They are used by the special operators "-in" and "-not_in" for generating correct SQL even when the argument is an empty array (see below).

logic

This determines the default logical operator for multiple WHERE statements in arrays or hashes. If absent, the default logic is "or" for arrays, and "and" for hashes. This means that a WHERE array of the form:

    @where = (
        event_date => {'>=', '2/13/99'},
        event_date => {'<=', '4/24/03'},
    );
    

will generate SQL like this:

    WHERE event_date >= '2/13/99' OR event_date <= '4/24/03'
    

This is probably not what you want given this query, though (look at the dates). To change the "OR" to an "AND", simply specify:

    my $sql = SQL::Abstract->new(logic => 'and');
    

Which will change the above "WHERE" to:

    WHERE event_date >= '2/13/99' AND event_date <= '4/24/03'
    

The logic can also be changed locally by inserting a modifier in front of an arrayref:

    @where = (-and => [event_date => {'>=', '2/13/99'},
                       event_date => {'<=', '4/24/03'} ]);
    

See the "WHERE CLAUSES" section for explanations.

convert

This will automatically convert comparisons using the specified SQL function for both column and value. This is mostly used with an argument of "upper" or "lower", so that the SQL will have the effect of case-insensitive "searches". For example, this:

    $sql = SQL::Abstract->new(convert => 'upper');
    %where = (keywords => 'MaKe iT CAse inSeNSItive');
    

Will turn out the following SQL:

    WHERE upper(keywords) like upper('MaKe iT CAse inSeNSItive')
    

The conversion can be "upper()", "lower()", or any other SQL function that can be applied symmetrically to fields (actually SQL::Abstract does not validate this option; it will just pass through what you specify verbatim).

bindtype

This is a kludge because many databases suck. For example, you can't just bind values using DBI's "execute()" for Oracle "CLOB" or "BLOB" fields. Instead, you have to use "bind_param()":

    $sth->bind_param(1, 'reg data');
    $sth->bind_param(2, $lots, {ora_type => ORA_CLOB});
    

The problem is, SQL::Abstract will normally just return a @bind array, which loses track of which field each slot refers to. Fear not.

If you specify "bindtype" in new, you can determine how @bind is returned. Currently, you can specify either "normal" (default) or "columns". If you specify "columns", you will get an array that looks like this:

    my $sql = SQL::Abstract->new(bindtype => 'columns');
    my($stmt, @bind) = $sql->insert(...);

    @bind = (
        [ 'column1', 'value1' ],
        [ 'column2', 'value2' ],
        [ 'column3', 'value3' ],
    );
    

You can then iterate through this manually, using DBI's "bind_param()".

    $sth->prepare($stmt);
    my $i = 1;
    for (@bind) {
        my($col, $data) = @$_;
        if ($col eq 'details' || $col eq 'comments') {
            $sth->bind_param($i, $data, {ora_type => ORA_CLOB});
        } elsif ($col eq 'image') {
            $sth->bind_param($i, $data, {ora_type => ORA_BLOB});
        } else {
            $sth->bind_param($i, $data);
        }
        $i++;
    }
    $sth->execute;      # execute without @bind now
    

Now, why would you still use SQL::Abstract if you have to do this crap? Basically, the advantage is still that you don't have to care which fields are or are not included. You could wrap that above "for" loop in a simple sub called "bind_fields()" or something and reuse it repeatedly. You still get a layer of abstraction over manual SQL specification.

Note that if you set "bindtype" to "columns", the "\[ $sql, @bind ]" construct (see "Literal SQL with placeholders and bind values (subqueries)") will expect the bind values in this format.

quote_char

This is the character that a table or column name will be quoted with. By default this is an empty string, but you could set it to the character "`", to generate SQL like this:

  SELECT `a_field` FROM `a_table` WHERE `some_field` LIKE '%someval%'
    

Alternatively, you can supply an array ref of two items, the first being the left hand quote character, and the second the right hand quote character. For example, you could supply "['[',']']" for SQL Server 2000 compliant quotes that generates SQL like this:

  SELECT [a_field] FROM [a_table] WHERE [some_field] LIKE '%someval%'
    

Quoting is useful if you have tables or columns names that are reserved words in your database's SQL dialect.

escape_char

This is the character that will be used to escape "quote_char"s appearing in an identifier before it has been quoted.

The parameter default in case of a single "quote_char" character is the quote character itself.

When opening-closing-style quoting is used ("quote_char" is an arrayref) this parameter defaults to the closing (right) "quote_char". Occurrences of the opening (left) "quote_char" within the identifier are currently left untouched. The default for opening-closing-style quotes may change in future versions, thus you are strongly encouraged to specify the escape character explicitly.

name_sep

This is the character that separates a table and column name. It is necessary to specify this when the "quote_char" option is selected, so that tables and column names can be individually quoted like this:

  SELECT `table`.`one_field` FROM `table` WHERE `table`.`other_field` = 1
    

injection_guard

A regular expression "qr/.../" that is applied to any "-function" and unquoted column name specified in a query structure. This is a safety mechanism to avoid injection attacks when mishandling user input e.g.:

  my %condition_as_column_value_pairs = get_values_from_user();
  $sqla->select( ... , \%condition_as_column_value_pairs );
    

If the expression matches an exception is thrown. Note that literal SQL supplied via "\'...'" or "\['...']" is not checked in any way.

Defaults to checking for ";" and the "GO" keyword (TransactSQL)

array_datatypes

When this option is true, arrayrefs in INSERT or UPDATE are interpreted as array datatypes and are passed directly to the DBI layer. When this option is false, arrayrefs are interpreted as literal SQL, just like refs to arrayrefs (but this behavior is for backwards compatibility; when writing new queries, use the "reference to arrayref" syntax for literal SQL).

special_ops

Takes a reference to a list of "special operators" to extend the syntax understood by SQL::Abstract. See section "SPECIAL OPERATORS" for details.

unary_ops

Takes a reference to a list of "unary operators" to extend the syntax understood by SQL::Abstract. See section "UNARY OPERATORS" for details.

insert($table, \@values || \%fieldvals, \%options)

The optional "\%options" hash reference may contain additional options to generate the insert SQL. Currently supported options are:

returning

Takes either a scalar of raw SQL fields, or an array reference of field names, and adds on an SQL "RETURNING" statement at the end. This allows you to return data generated by the insert statement (such as row IDs) without performing another "SELECT" statement. Note, however, this is not part of the SQL standard and may not be supported by all database engines.

update($table, \%fieldvals, \%where, \%options)

The optional "\%options" hash reference may contain additional options to generate the update SQL. Currently supported options are:

returning

See the "returning" option to insert.

select($source, $fields, $where, $order)

$source

Specification of the 'FROM' part of the statement. The argument can be either a plain scalar (interpreted as a table name, will be quoted), or an arrayref (interpreted as a list of table names, joined by commas, quoted), or a scalarref (literal SQL, not quoted).

$fields

Specification of the list of fields to retrieve from the source. The argument can be either an arrayref (interpreted as a list of field names, will be joined by commas and quoted), or a plain scalar (literal SQL, not quoted). Please observe that this API is not as flexible as that of the first argument $source, for backwards compatibility reasons.

$where

Optional argument to specify the WHERE part of the query. The argument is most often a hashref, but can also be an arrayref or plain scalar -- see section WHERE clause for details.

$order

Optional argument to specify the ORDER BY part of the query. The argument can be a scalar, a hashref or an arrayref -- see section ORDER BY clause for details.

delete($table, \%where, \%options)

The optional "\%options" hash reference may contain additional options to generate the delete SQL. Currently supported options are:

returning

See the "returning" option to insert.

where(\%where, $order)

values(\%data)

generate($any, 'number', $of, \@data, $struct, \%types)

This returns arbitrarily generated SQL. It's a really basic shortcut. It will return two different things, depending on return context:

    my($stmt, @bind) = $sql->generate('create table', \$table, \@fields);
    my $stmt_and_val = $sql->generate('create table', \$table, \@fields);

These would return the following:

    # First calling form
    $stmt = "CREATE TABLE test (?, ?)";
    @bind = (field1, field2);

    # Second calling form
    $stmt_and_val = "CREATE TABLE test (field1, field2)";

Depending on what you're trying to do, it's up to you to choose the correct format. In this example, the second form is what you would want.

By the same token:

    $sql->generate('alter session', { nls_date_format => 'MM/YY' });

Might give you:

    ALTER SESSION SET nls_date_format = 'MM/YY'

You get the idea. Strings get their case twiddled, but everything else remains verbatim.

is_plain_value

• The value is "undef"
• The value is a non-reference
• The value is an object with stringification overloading
• The value is of the form "{ -value => $anything }"

On failure returns "undef", on success returns a scalar reference to the original supplied argument.

•

Note

The stringification overloading detection is rather advanced: it takes into consideration not only the presence of a "" overload, but if that fails also checks for enabled autogenerated versions of "", based on either "0+" or "bool".

Unfortunately testing in the field indicates that this detection may tickle a latent bug in perl versions before 5.018, but only when very large numbers of stringifying objects are involved. At the time of writing ( Sep 2014 ) there is no clear explanation of the direct cause, nor is there a manageably small test case that reliably reproduces the problem.

If you encounter any of the following exceptions in random places within your application stack - this module may be to blame:

  Operation "ne": no method found,
    left argument in overloaded package <something>,
    right argument in overloaded package <something>
    

or perhaps even

  Stub found while resolving method "???" overloading """" in package <something>
    

If you fall victim to the above - please attempt to reduce the problem to something that could be sent to the SQL::Abstract developers

(either publicly or privately). As a workaround in the meantime you can set $ENV{SQLA_ISVALUE_IGNORE_AUTOGENERATED_STRINGIFICATION} to a true value, which will most likely eliminate your problem (at the expense of not being able to properly detect exotic forms of stringification).

This notice and environment variable will be removed in a future version, as soon as the underlying problem is found and a reliable workaround is devised.

is_literal_value

• "\$sql_string"
• "\[ $sql_string, @bind_values ]"

On failure returns "undef", on success returns an array reference containing the unpacked version of the supplied literal SQL and bind values.

is_undef_value

Introduction

The easiest way to explain is to show lots of examples. After each %where hash shown, it is assumed you used:

    my($stmt, @bind) = $sql->where(\%where);

However, note that the %where hash can be used directly in any of the other functions as well, as described above.

Key-value pairs

    my %where  = (
        user   => 'nwiger',
        status => 'completed'
    );

Is converted to SQL "key = val" statements:

    $stmt = "WHERE user = ? AND status = ?";
    @bind = ('nwiger', 'completed');

One common thing I end up doing is having a list of values that a field can be in. To do this, simply specify a list inside of an arrayref:

    my %where  = (
        user   => 'nwiger',
        status => ['assigned', 'in-progress', 'pending'];
    );

This simple code will create the following:

    $stmt = "WHERE user = ? AND ( status = ? OR status = ? OR status = ? )";
    @bind = ('nwiger', 'assigned', 'in-progress', 'pending');

A field associated to an empty arrayref will be considered a logical false and will generate 0=1.

Tests for NULL values

    my %where  = (
        user   => 'nwiger',
        status => undef,
    );

becomes:

    $stmt = "WHERE user = ? AND status IS NULL";
    @bind = ('nwiger');

To test if a column IS NOT NULL:

    my %where  = (
        user   => 'nwiger',
        status => { '!=', undef },
    );

Specific comparison operators

    my %where  = (
        user   => 'nwiger',
        status => { '!=', 'completed' }
    );

Which would generate:

    $stmt = "WHERE user = ? AND status != ?";
    @bind = ('nwiger', 'completed');

To test against multiple values, just enclose the values in an arrayref:

    status => { '=', ['assigned', 'in-progress', 'pending'] };

Which would give you:

    "WHERE status = ? OR status = ? OR status = ?"

The hashref can also contain multiple pairs, in which case it is expanded into an "AND" of its elements:

    my %where  = (
        user   => 'nwiger',
        status => { '!=', 'completed', -not_like => 'pending%' }
    );

    # Or more dynamically, like from a form
    $where{user} = 'nwiger';
    $where{status}{'!='} = 'completed';
    $where{status}{'-not_like'} = 'pending%';

    # Both generate this
    $stmt = "WHERE user = ? AND status != ? AND status NOT LIKE ?";
    @bind = ('nwiger', 'completed', 'pending%');

To get an OR instead, you can combine it with the arrayref idea:

    my %where => (
         user => 'nwiger',
         priority => [ { '=', 2 }, { '>', 5 } ]
    );

Which would generate:

    $stmt = "WHERE ( priority = ? OR priority > ? ) AND user = ?";
    @bind = ('2', '5', 'nwiger');

If you want to include literal SQL (with or without bind values), just use a scalar reference or reference to an arrayref as the value:

    my %where  = (
        date_entered => { '>' => \["to_date(?, 'MM/DD/YYYY')", "11/26/2008"] },
        date_expires => { '<' => \"now()" }
    );

Which would generate:

    $stmt = "WHERE date_entered > to_date(?, 'MM/DD/YYYY') AND date_expires < now()";
    @bind = ('11/26/2008');

Logic and nesting operators

    WHERE priority != ? AND priority != ?

Because, in Perl you can't do this:

    priority => { '!=' => 2, '!=' => 1 }

As the second "!=" key will obliterate the first. The solution is to use the special "-modifier" form inside an arrayref:

    priority => [ -and => {'!=', 2},
                          {'!=', 1} ]

Normally, these would be joined by "OR", but the modifier tells it to use "AND" instead. (Hint: You can use this in conjunction with the "logic" option to "new()" in order to change the way your queries work by default.) Important: Note that the "-modifier" goes INSIDE the arrayref, as an extra first element. This will NOT do what you think it might:

    priority => -and => [{'!=', 2}, {'!=', 1}]   # WRONG!

Here is a quick list of equivalencies, since there is some overlap:

    # Same
    status => {'!=', 'completed', 'not like', 'pending%' }
    status => [ -and => {'!=', 'completed'}, {'not like', 'pending%'}]

    # Same
    status => {'=', ['assigned', 'in-progress']}
    status => [ -or => {'=', 'assigned'}, {'=', 'in-progress'}]
    status => [ {'=', 'assigned'}, {'=', 'in-progress'} ]

Special operators: IN, BETWEEN, etc.

    my %where  = (
        status   => 'completed',
        reportid => { -in => [567, 2335, 2] }
    );

Which would generate:

    $stmt = "WHERE status = ? AND reportid IN (?,?,?)";
    @bind = ('completed', '567', '2335', '2');

The reverse operator "-not_in" generates SQL "NOT IN" and is used in the same way.

If the argument to "-in" is an empty array, 'sqlfalse' is generated (by default: "1=0"). Similarly, "-not_in => []" generates 'sqltrue' (by default: "1=1").

In addition to the array you can supply a chunk of literal sql or literal sql with bind:

    my %where = {
      customer => { -in => \[
        'SELECT cust_id FROM cust WHERE balance > ?',
        2000,
      ],
      status => { -in => \'SELECT status_codes FROM states' },
    };

would generate:

    $stmt = "WHERE (
          customer IN ( SELECT cust_id FROM cust WHERE balance > ? )
      AND status IN ( SELECT status_codes FROM states )
    )";
    @bind = ('2000');

Finally, if the argument to "-in" is not a reference, it will be treated as a single-element array.

Another pair of operators is "-between" and "-not_between", used with an arrayref of two values:

    my %where  = (
        user   => 'nwiger',
        completion_date => {
           -not_between => ['2002-10-01', '2003-02-06']
        }
    );

Would give you:

    WHERE user = ? AND completion_date NOT BETWEEN ( ? AND ? )

Just like with "-in" all plausible combinations of literal SQL are possible:

    my %where = {
      start0 => { -between => [ 1, 2 ] },
      start1 => { -between => \["? AND ?", 1, 2] },
      start2 => { -between => \"lower(x) AND upper(y)" },
      start3 => { -between => [
        \"lower(x)",
        \["upper(?)", 'stuff' ],
      ] },
    };

Would give you:

    $stmt = "WHERE (
          ( start0 BETWEEN ? AND ?                )
      AND ( start1 BETWEEN ? AND ?                )
      AND ( start2 BETWEEN lower(x) AND upper(y)  )
      AND ( start3 BETWEEN lower(x) AND upper(?)  )
    )";
    @bind = (1, 2, 1, 2, 'stuff');

These are the two builtin "special operators"; but the list can be expanded: see section "SPECIAL OPERATORS" below.

Unary operators: bool

    my %where  = (
        -bool       => 'is_user',
        -not_bool   => 'is_enabled',
    );

Would give you:

    WHERE is_user AND NOT is_enabled

If a more complex combination is required, testing more conditions, then you should use the and/or operators:-

    my %where  = (
        -and           => [
            -bool      => 'one',
            -not_bool  => { two=> { -rlike => 'bar' } },
            -not_bool  => { three => [ { '=', 2 }, { '>', 5 } ] },
        ],
    );

Would give you:

    WHERE
      one
        AND
      (NOT two RLIKE ?)
        AND
      (NOT ( three = ? OR three > ? ))

Nested conditions, -and/-or prefixes

    my @where = (
        {
            user   => 'nwiger',
            status => { -like => ['pending%', 'dispatched'] },
        },
        {
            user   => 'robot',
            status => 'unassigned',
        }
    );

This data structure would create the following:

    $stmt = "WHERE ( user = ? AND ( status LIKE ? OR status LIKE ? ) )
                OR ( user = ? AND status = ? ) )";
    @bind = ('nwiger', 'pending', 'dispatched', 'robot', 'unassigned');

Clauses in hashrefs or arrayrefs can be prefixed with an "-and" or "-or" to change the logic inside:

    my @where = (
         -and => [
            user => 'nwiger',
            [
                -and => [ workhrs => {'>', 20}, geo => 'ASIA' ],
                -or => { workhrs => {'<', 50}, geo => 'EURO' },
            ],
        ],
    );

That would yield:

    $stmt = "WHERE ( user = ?
               AND ( ( workhrs > ? AND geo = ? )
                  OR ( workhrs < ? OR geo = ? ) ) )";
    @bind = ('nwiger', '20', 'ASIA', '50', 'EURO');

Algebraic inconsistency, for historical reasons

"Important note": when connecting several conditions, the "-and-"|"-or" operator goes "outside" of the nested structure; whereas when connecting several constraints on one column, the "-and" operator goes "inside" the arrayref. Here is an example combining both features:

   my @where = (
     -and => [a => 1, b => 2],
     -or  => [c => 3, d => 4],
      e   => [-and => {-like => 'foo%'}, {-like => '%bar'} ]
   )

yielding

  WHERE ( (    ( a = ? AND b = ? )
            OR ( c = ? OR d = ? )
            OR ( e LIKE ? AND e LIKE ? ) ) )

This difference in syntax is unfortunate but must be preserved for historical reasons. So be careful: the two examples below would seem algebraically equivalent, but they are not

  { col => [ -and =>
    { -like => 'foo%' },
    { -like => '%bar' },
  ] }
  # yields: WHERE ( ( col LIKE ? AND col LIKE ? ) )

  [ -and =>
    { col => { -like => 'foo%' } },
    { col => { -like => '%bar' } },
  ]
  # yields: WHERE ( ( col LIKE ? OR col LIKE ? ) )

Literal SQL and value type operators

-ident

This is a virtual operator that signals the string to its right side is an identifier (a column name) and not a value. For example to compare two columns you would write:

    my %where = (
        priority => { '<', 2 },
        requestor => { -ident => 'submitter' },
    );

which creates:

    $stmt = "WHERE priority < ? AND requestor = submitter";
    @bind = ('2');

If you are maintaining legacy code you may see a different construct as described in "Deprecated usage of Literal SQL", please use "-ident" in new code.

-value

This is a virtual operator that signals that the construct to its right side is a value to be passed to DBI. This is for example necessary when you want to write a where clause against an array (for RDBMS that support such datatypes). For example:

    my %where = (
        array => { -value => [1, 2, 3] }
    );

will result in:

    $stmt = 'WHERE array = ?';
    @bind = ([1, 2, 3]);

Note that if you were to simply say:

    my %where = (
        array => [1, 2, 3]
    );

the result would probably not be what you wanted:

    $stmt = 'WHERE array = ? OR array = ? OR array = ?';
    @bind = (1, 2, 3);

Literal SQL

Finally, sometimes only literal SQL will do. To include a random snippet of SQL verbatim, you specify it as a scalar reference. Consider this only as a last resort. Usually there is a better way. For example:

    my %where = (
        priority => { '<', 2 },
        requestor => { -in => \'(SELECT name FROM hitmen)' },
    );

Would create:

    $stmt = "WHERE priority < ? AND requestor IN (SELECT name FROM hitmen)"
    @bind = (2);

Note that in this example, you only get one bind parameter back, since the verbatim SQL is passed as part of the statement.

CAVEAT

  Never use untrusted input as a literal SQL argument - this is a massive
  security risk (there is no way to check literal snippets for SQL
  injections and other nastyness). If you need to deal with untrusted input
  use literal SQL with placeholders as described next.

Literal SQL with placeholders and bind values (subqueries)

If the literal SQL to be inserted has placeholders and bind values, use a reference to an arrayref (yes this is a double reference -- not so common, but perfectly legal Perl). For example, to find a date in Postgres you can use something like this:

    my %where = (
       date_column => \[ "= date '2008-09-30' - ?::integer", 10 ]
    )

This would create:

    $stmt = "WHERE ( date_column = date '2008-09-30' - ?::integer )"
    @bind = ('10');

Note that you must pass the bind values in the same format as they are returned by where. This means that if you set "bindtype" to "columns", you must provide the bind values in the "[ column_meta => value ]" format, where "column_meta" is an opaque scalar value; most commonly the column name, but you can use any scalar value (including references and blessed references), SQL::Abstract will simply pass it through intact. So if "bindtype" is set to "columns" the above example will look like:

    my %where = (
       date_column => \[ "= date '2008-09-30' - ?::integer", [ {} => 10 ] ]
    )

Literal SQL is especially useful for nesting parenthesized clauses in the main SQL query. Here is a first example:

  my ($sub_stmt, @sub_bind) = ("SELECT c1 FROM t1 WHERE c2 < ? AND c3 LIKE ?",
                               100, "foo%");
  my %where = (
    foo => 1234,
    bar => \["IN ($sub_stmt)" => @sub_bind],
  );

This yields:

  $stmt = "WHERE (foo = ? AND bar IN (SELECT c1 FROM t1
                                             WHERE c2 < ? AND c3 LIKE ?))";
  @bind = (1234, 100, "foo%");

Other subquery operators, like for example "> ALL" or "NOT IN", are expressed in the same way. Of course the $sub_stmt and its associated bind values can be generated through a former call to "select()" :

  my ($sub_stmt, @sub_bind)
     = $sql->select("t1", "c1", {c2 => {"<" => 100},
                                 c3 => {-like => "foo%"}});
  my %where = (
    foo => 1234,
    bar => \["> ALL ($sub_stmt)" => @sub_bind],
  );

In the examples above, the subquery was used as an operator on a column; but the same principle also applies for a clause within the main %where hash, like an EXISTS subquery:

  my ($sub_stmt, @sub_bind)
     = $sql->select("t1", "*", {c1 => 1, c2 => \"> t0.c0"});
  my %where = ( -and => [
    foo   => 1234,
    \["EXISTS ($sub_stmt)" => @sub_bind],
  ]);

which yields

  $stmt = "WHERE (foo = ? AND EXISTS (SELECT * FROM t1
                                        WHERE c1 = ? AND c2 > t0.c0))";
  @bind = (1234, 1);

Observe that the condition on "c2" in the subquery refers to column "t0.c0" of the main query: this is not a bind value, so we have to express it through a scalar ref. Writing "c2 => {">" => "t0.c0"}" would have generated "c2 > ?" with bind value "t0.c0" ... not exactly what we wanted here.

Finally, here is an example where a subquery is used for expressing unary negation:

  my ($sub_stmt, @sub_bind)
     = $sql->where({age => [{"<" => 10}, {">" => 20}]});
  $sub_stmt =~ s/^ where //i; # don't want "WHERE" in the subclause
  my %where = (
        lname  => {like => '%son%'},
        \["NOT ($sub_stmt)" => @sub_bind],
    );

This yields

  $stmt = "lname LIKE ? AND NOT ( age < ? OR age > ? )"
  @bind = ('%son%', 10, 20)

Deprecated usage of Literal SQL

Below are some examples of archaic use of literal SQL. It is shown only as reference for those who deal with legacy code. Each example has a much better, cleaner and safer alternative that users should opt for in new code.

•     my %where = ( requestor => \'IS NOT NULL' )
  
      $stmt = "WHERE requestor IS NOT NULL"
      

  This used to be the way of generating NULL comparisons, before the handling of "undef" got formalized. For new code please use the superior syntax as described in "Tests for NULL values".

•     my %where = ( requestor => \'= submitter' )
  
      $stmt = "WHERE requestor = submitter"
      

  This used to be the only way to compare columns. Use the superior "-ident" method for all new code. For example an identifier declared in such a way will be properly quoted if "quote_char" is properly set, while the legacy form will remain as supplied.

•     my %where = ( is_ready  => \"", completed => { '>', '2012-12-21' } )
  
      $stmt = "WHERE completed > ? AND is_ready"
      @bind = ('2012-12-21')
      

  Using an empty string literal used to be the only way to express a boolean. For all new code please use the much more readable -bool operator.

Conclusion

And of course, all the values above will probably be replaced with variables gotten from forms or the command line. After all, if you knew everything ahead of time, you wouldn't have to worry about dynamically-generating SQL and could just hardwire it into your script.

SPECIAL OPERATORS

  my $sqlmaker = SQL::Abstract->new(special_ops => [
     {
      regex => qr/.../,
      handler => sub {
        my ($self, $field, $op, $arg) = @_;
        ...
      },
     },
     {
      regex => qr/.../,
      handler => 'method_name',
     },
   ]);

A "special operator" is a SQL syntactic clause that can be applied to a field, instead of a usual binary operator. For example:

   WHERE field IN (?, ?, ?)
   WHERE field BETWEEN ? AND ?
   WHERE MATCH(field) AGAINST (?, ?)

Special operators IN and BETWEEN are fairly standard and therefore are builtin within "SQL::Abstract" (as the overridable methods "_where_field_IN" and "_where_field_BETWEEN"). For other operators, like the MATCH .. AGAINST example above which is specific to MySQL, you can write your own operator handlers - supply a "special_ops" argument to the "new" method. That argument takes an arrayref of operator definitions; each operator definition is a hashref with two entries:

regex

the regular expression to match the operator

handler

Either a coderef or a plain scalar method name. In both cases the expected return is "($sql, @bind)".

When supplied with a method name, it is simply called on the SQL::Abstract object as:

 $self->$method_name($field, $op, $arg)

 Where:

  $field is the LHS of the operator
  $op is the part that matched the handler regex
  $arg is the RHS
    

When supplied with a coderef, it is called as:

 $coderef->($self, $field, $op, $arg)
    

For example, here is an implementation of the MATCH .. AGAINST syntax for MySQL

  my $sqlmaker = SQL::Abstract->new(special_ops => [

    # special op for MySql MATCH (field) AGAINST(word1, word2, ...)
    {regex => qr/^match$/i,
     handler => sub {
       my ($self, $field, $op, $arg) = @_;
       $arg = [$arg] if not ref $arg;
       my $label         = $self->_quote($field);
       my ($placeholder) = $self->_convert('?');
       my $placeholders  = join ", ", (($placeholder) x @$arg);
       my $sql           = $self->_sqlcase('match') . " ($label) "
                         . $self->_sqlcase('against') . " ($placeholders) ";
       my @bind = $self->_bindtype($field, @$arg);
       return ($sql, @bind);
       }
     },

  ]);

UNARY OPERATORS

  my $sqlmaker = SQL::Abstract->new(unary_ops => [
     {
      regex => qr/.../,
      handler => sub {
        my ($self, $op, $arg) = @_;
        ...
      },
     },
     {
      regex => qr/.../,
      handler => 'method_name',
     },
   ]);

A "unary operator" is a SQL syntactic clause that can be applied to a field - the operator goes before the field

You can write your own operator handlers - supply a "unary_ops" argument to the "new" method. That argument takes an arrayref of operator definitions; each operator definition is a hashref with two entries:

regex

the regular expression to match the operator

handler

Either a coderef or a plain scalar method name. In both cases the expected return is $sql.

When supplied with a method name, it is simply called on the SQL::Abstract object as:

 $self->$method_name($op, $arg)

 Where:

  $op is the part that matched the handler regex
  $arg is the RHS or argument of the operator
    

When supplied with a coderef, it is called as:

 $coderef->($self, $op, $arg)
    

plugin

  $sqla->plugin('+Foo');

Enables plugin SQL::Abstract::Plugin::Foo.

render_expr

  my ($sql, @bind) = $sqla->render_expr($expr);

render_statement

  my ($sql, @bind) = $sqla->render_statement($expr);

expand_expr

  my $aqt = $self->expand_expr($expr);
  my $aqt = $self->expand_expr($expr, -ident);

render_aqt

  my $res = $self->render_aqt($aqt, $top_level);
  my ($sql, @bind) = @$res;

join_query_parts

  my $part = $self->join_query_parts($join, @parts);

clone

  my $sqla2 = $sqla->clone;

Performs a semi-shallow copy such that extension methods won't leak state but excessive depth is avoided.

expander

expanders

op_expander

op_expanders

clause_expander

clause_expanders

  $sqla->expander('name' => sub { ... });
  $sqla->expanders('name1' => sub { ... }, 'name2' => sub { ... });

expander_list

op_expander_list

clause_expander_list

  my @names = $sqla->expander_list;

wrap_expander

wrap_expanders

wrap_op_expander

wrap_op_expanders

wrap_clause_expander

wrap_clause_expanders

  $sqla->wrap_expander('name' => sub { my ($orig) = @_; sub { ... } });
  $sqla->wrap_expanders(
    'name1' => sub { my ($orig1) = @_; sub { ... } },
    'name2' => sub { my ($orig2) = @_; sub { ... } },
  );

renderer

renderers

op_renderer

op_renderers

clause_renderer

clause_renderers

  $sqla->renderer('name' => sub { ... });
  $sqla->renderers('name1' => sub { ... }, 'name2' => sub { ... });

renderer_list

op_renderer_list

clause_renderer_list

  my @names = $sqla->renderer_list;

wrap_renderer

wrap_renderers

wrap_op_renderer

wrap_op_renderers

wrap_clause_renderer

wrap_clause_renderers

  $sqla->wrap_renderer('name' => sub { my ($orig) = @_; sub { ... } });
  $sqla->wrap_renderers(
    'name1' => sub { my ($orig1) = @_; sub { ... } },
    'name2' => sub { my ($orig2) = @_; sub { ... } },
  );

clauses_of

  my @clauses = $sqla->clauses_of('select');
  $sqla->clauses_of(select => \@new_clauses);
  $sqla->clauses_of(select => sub {
    my (undef, @old_clauses) = @_;
    ...
    return @new_clauses;
  });

statement_list

  my @list = $sqla->statement_list;

make_unop_expander

  my $exp = $sqla->make_unop_expander(sub { ... });

If the op is found as a binop, assumes it wants a default comparison, so the inner expander sub can reliably operate as

  sub { my ($self, $name, $body) = @_; ... }

make_binop_expander

  my $exp = $sqla->make_binop_expander(sub { ... });

If the op is found as a unop, assumes the value will be an arrayref with the LHS as the first entry, and converts that to an ident node if it's a simple scalar. So the inner expander sub looks like

  sub {
    my ($self, $name, $body, $k) = @_;
    { -blah => [ map $self->expand_expr($_), $k, $body ] }
  }

unop_expander

unop_expanders

binop_expander

binop_expanders