1 package SQL::Abstract; # see doc at end of file
10 our @EXPORT_OK = qw(is_plain_value is_literal_value);
20 *SQL::Abstract::_ENV_::DETECT_AUTOGENERATED_STRINGIFICATION = $ENV{SQLA_ISVALUE_IGNORE_AUTOGENERATED_STRINGIFICATION}
26 #======================================================================
28 #======================================================================
30 our $VERSION = '1.87';
32 # This would confuse some packagers
33 $VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases
37 # special operators (-in, -between). May be extended/overridden by user.
38 # See section WHERE: BUILTIN SPECIAL OPERATORS below for implementation
39 my @BUILTIN_SPECIAL_OPS = (
40 {regex => qr/^ (?: not \s )? between $/ix, handler => sub { die "NOPE" }},
41 {regex => qr/^ (?: not \s )? in $/ix, handler => sub { die "NOPE" }},
42 {regex => qr/^ is (?: \s+ not )? $/ix, handler => sub { die "NOPE" }},
45 #======================================================================
46 # DEBUGGING AND ERROR REPORTING
47 #======================================================================
50 return unless $_[0]->{debug}; shift; # a little faster
51 my $func = (caller(1))[3];
52 warn "[$func] ", @_, "\n";
56 my($func) = (caller(1))[3];
57 Carp::carp "[$func] Warning: ", @_;
61 my($func) = (caller(1))[3];
62 Carp::croak "[$func] Fatal: ", @_;
65 sub is_literal_value ($) {
66 ref $_[0] eq 'SCALAR' ? [ ${$_[0]} ]
67 : ( ref $_[0] eq 'REF' and ref ${$_[0]} eq 'ARRAY' ) ? [ @${ $_[0] } ]
71 # FIXME XSify - this can be done so much more efficiently
72 sub is_plain_value ($) {
74 ! length ref $_[0] ? \($_[0])
76 ref $_[0] eq 'HASH' and keys %{$_[0]} == 1
78 exists $_[0]->{-value}
79 ) ? \($_[0]->{-value})
81 # reuse @_ for even moar speedz
82 defined ( $_[1] = Scalar::Util::blessed $_[0] )
84 # deliberately not using Devel::OverloadInfo - the checks we are
85 # intersted in are much more limited than the fullblown thing, and
86 # this is a very hot piece of code
88 # simply using ->can('(""') can leave behind stub methods that
89 # break actually using the overload later (see L<perldiag/Stub
90 # found while resolving method "%s" overloading "%s" in package
91 # "%s"> and the source of overload::mycan())
93 # either has stringification which DBI SHOULD prefer out of the box
94 grep { *{ (qq[${_}::(""]) }{CODE} } @{ $_[2] = mro::get_linear_isa( $_[1] ) }
96 # has nummification or boolification, AND fallback is *not* disabled
98 SQL::Abstract::_ENV_::DETECT_AUTOGENERATED_STRINGIFICATION
101 grep { *{"${_}::(0+"}{CODE} } @{$_[2]}
103 grep { *{"${_}::(bool"}{CODE} } @{$_[2]}
107 # no fallback specified at all
108 ! ( ($_[3]) = grep { *{"${_}::()"}{CODE} } @{$_[2]} )
110 # fallback explicitly undef
111 ! defined ${"$_[3]::()"}
124 #======================================================================
126 #======================================================================
130 my $class = ref($self) || $self;
131 my %opt = (ref $_[0] eq 'HASH') ? %{$_[0]} : @_;
133 # choose our case by keeping an option around
134 delete $opt{case} if $opt{case} && $opt{case} ne 'lower';
136 # default logic for interpreting arrayrefs
137 $opt{logic} = $opt{logic} ? uc $opt{logic} : 'OR';
139 # how to return bind vars
140 $opt{bindtype} ||= 'normal';
142 # default comparison is "=", but can be overridden
145 # try to recognize which are the 'equality' and 'inequality' ops
146 # (temporary quickfix (in 2007), should go through a more seasoned API)
147 $opt{equality_op} = qr/^( \Q$opt{cmp}\E | \= )$/ix;
148 $opt{inequality_op} = qr/^( != | <> )$/ix;
150 $opt{like_op} = qr/^ (is\s+)? r?like $/xi;
151 $opt{not_like_op} = qr/^ (is\s+)? not \s+ r?like $/xi;
154 $opt{sqltrue} ||= '1=1';
155 $opt{sqlfalse} ||= '0=1';
158 $opt{user_special_ops} = [ @{$opt{special_ops} ||= []} ];
159 # regexes are applied in order, thus push after user-defines
160 push @{$opt{special_ops}}, @BUILTIN_SPECIAL_OPS;
163 $opt{unary_ops} ||= [];
165 # rudimentary sanity-check for user supplied bits treated as functions/operators
166 # If a purported function matches this regular expression, an exception is thrown.
167 # Literal SQL is *NOT* subject to this check, only functions (and column names
168 # when quoting is not in effect)
171 # need to guard against ()'s in column names too, but this will break tons of
172 # hacks... ideas anyone?
173 $opt{injection_guard} ||= qr/
179 return bless \%opt, $class;
182 sub sqltrue { +{ -literal => [ $_[0]->{sqltrue} ] } }
183 sub sqlfalse { +{ -literal => [ $_[0]->{sqlfalse} ] } }
185 sub _assert_pass_injection_guard {
186 if ($_[1] =~ $_[0]->{injection_guard}) {
187 my $class = ref $_[0];
188 puke "Possible SQL injection attempt '$_[1]'. If this is indeed a part of the "
189 . "desired SQL use literal SQL ( \'...' or \[ '...' ] ) or supply your own "
190 . "{injection_guard} attribute to ${class}->new()"
195 #======================================================================
197 #======================================================================
201 my $table = $self->_table(shift);
202 my $data = shift || return;
205 my $method = $self->_METHOD_FOR_refkind("_insert", $data);
206 my ($sql, @bind) = $self->$method($data);
207 $sql = join " ", $self->_sqlcase('insert into'), $table, $sql;
209 if ($options->{returning}) {
210 my ($s, @b) = $self->_insert_returning($options);
215 return wantarray ? ($sql, @bind) : $sql;
218 # So that subclasses can override INSERT ... RETURNING separately from
219 # UPDATE and DELETE (e.g. DBIx::Class::SQLMaker::Oracle does this)
220 sub _insert_returning { shift->_returning(@_) }
223 my ($self, $options) = @_;
225 my $f = $options->{returning};
227 my $fieldlist = $self->_SWITCH_refkind($f, {
228 ARRAYREF => sub {join ', ', map { $self->_quote($_) } @$f;},
229 SCALAR => sub {$self->_quote($f)},
230 SCALARREF => sub {$$f},
232 return $self->_sqlcase(' returning ') . $fieldlist;
235 sub _insert_HASHREF { # explicit list of fields and then values
236 my ($self, $data) = @_;
238 my @fields = sort keys %$data;
240 my ($sql, @bind) = $self->_insert_values($data);
243 $_ = $self->_quote($_) foreach @fields;
244 $sql = "( ".join(", ", @fields).") ".$sql;
246 return ($sql, @bind);
249 sub _insert_ARRAYREF { # just generate values(?,?) part (no list of fields)
250 my ($self, $data) = @_;
252 # no names (arrayref) so can't generate bindtype
253 $self->{bindtype} ne 'columns'
254 or belch "can't do 'columns' bindtype when called with arrayref";
256 my (@values, @all_bind);
257 foreach my $value (@$data) {
258 my ($values, @bind) = $self->_insert_value(undef, $value);
259 push @values, $values;
260 push @all_bind, @bind;
262 my $sql = $self->_sqlcase('values')." ( ".join(", ", @values)." )";
263 return ($sql, @all_bind);
266 sub _insert_ARRAYREFREF { # literal SQL with bind
267 my ($self, $data) = @_;
269 my ($sql, @bind) = @${$data};
270 $self->_assert_bindval_matches_bindtype(@bind);
272 return ($sql, @bind);
276 sub _insert_SCALARREF { # literal SQL without bind
277 my ($self, $data) = @_;
283 my ($self, $data) = @_;
285 my (@values, @all_bind);
286 foreach my $column (sort keys %$data) {
287 my ($values, @bind) = $self->_insert_value($column, $data->{$column});
288 push @values, $values;
289 push @all_bind, @bind;
291 my $sql = $self->_sqlcase('values')." ( ".join(", ", @values)." )";
292 return ($sql, @all_bind);
296 my ($self, $column, $v) = @_;
298 my (@values, @all_bind);
299 $self->_SWITCH_refkind($v, {
302 if ($self->{array_datatypes}) { # if array datatype are activated
304 push @all_bind, $self->_bindtype($column, $v);
306 else { # else literal SQL with bind
307 my ($sql, @bind) = @$v;
308 $self->_assert_bindval_matches_bindtype(@bind);
310 push @all_bind, @bind;
314 ARRAYREFREF => sub { # literal SQL with bind
315 my ($sql, @bind) = @${$v};
316 $self->_assert_bindval_matches_bindtype(@bind);
318 push @all_bind, @bind;
321 # THINK: anything useful to do with a HASHREF ?
322 HASHREF => sub { # (nothing, but old SQLA passed it through)
323 #TODO in SQLA >= 2.0 it will die instead
324 belch "HASH ref as bind value in insert is not supported";
326 push @all_bind, $self->_bindtype($column, $v);
329 SCALARREF => sub { # literal SQL without bind
333 SCALAR_or_UNDEF => sub {
335 push @all_bind, $self->_bindtype($column, $v);
340 my $sql = join(", ", @values);
341 return ($sql, @all_bind);
346 #======================================================================
348 #======================================================================
353 my $table = $self->_table(shift);
354 my $data = shift || return;
358 # first build the 'SET' part of the sql statement
359 puke "Unsupported data type specified to \$sql->update"
360 unless ref $data eq 'HASH';
362 my ($sql, @all_bind) = $self->_update_set_values($data);
363 $sql = $self->_sqlcase('update ') . $table . $self->_sqlcase(' set ')
367 my($where_sql, @where_bind) = $self->where($where);
369 push @all_bind, @where_bind;
372 if ($options->{returning}) {
373 my ($returning_sql, @returning_bind) = $self->_update_returning($options);
374 $sql .= $returning_sql;
375 push @all_bind, @returning_bind;
378 return wantarray ? ($sql, @all_bind) : $sql;
381 sub _update_set_values {
382 my ($self, $data) = @_;
384 my (@set, @all_bind);
385 for my $k (sort keys %$data) {
388 my $label = $self->_quote($k);
390 $self->_SWITCH_refkind($v, {
392 if ($self->{array_datatypes}) { # array datatype
393 push @set, "$label = ?";
394 push @all_bind, $self->_bindtype($k, $v);
396 else { # literal SQL with bind
397 my ($sql, @bind) = @$v;
398 $self->_assert_bindval_matches_bindtype(@bind);
399 push @set, "$label = $sql";
400 push @all_bind, @bind;
403 ARRAYREFREF => sub { # literal SQL with bind
404 my ($sql, @bind) = @${$v};
405 $self->_assert_bindval_matches_bindtype(@bind);
406 push @set, "$label = $sql";
407 push @all_bind, @bind;
409 SCALARREF => sub { # literal SQL without bind
410 push @set, "$label = $$v";
413 my ($op, $arg, @rest) = %$v;
415 puke 'Operator calls in update must be in the form { -op => $arg }'
416 if (@rest or not $op =~ /^\-(.+)/);
418 local our $Cur_Col_Meta = $k;
419 my ($sql, @bind) = $self->_render_expr(
420 $self->_expand_expr_hashpair($op, $arg)
423 push @set, "$label = $sql";
424 push @all_bind, @bind;
426 SCALAR_or_UNDEF => sub {
427 push @set, "$label = ?";
428 push @all_bind, $self->_bindtype($k, $v);
434 my $sql = join ', ', @set;
436 return ($sql, @all_bind);
439 # So that subclasses can override UPDATE ... RETURNING separately from
441 sub _update_returning { shift->_returning(@_) }
445 #======================================================================
447 #======================================================================
452 my $table = $self->_table(shift);
453 my $fields = shift || '*';
457 my ($fields_sql, @bind) = $self->_select_fields($fields);
459 my ($where_sql, @where_bind) = $self->where($where, $order);
460 push @bind, @where_bind;
462 my $sql = join(' ', $self->_sqlcase('select'), $fields_sql,
463 $self->_sqlcase('from'), $table)
466 return wantarray ? ($sql, @bind) : $sql;
470 my ($self, $fields) = @_;
471 return ref $fields eq 'ARRAY' ? join ', ', map { $self->_quote($_) } @$fields
475 #======================================================================
477 #======================================================================
482 my $table = $self->_table(shift);
486 my($where_sql, @bind) = $self->where($where);
487 my $sql = $self->_sqlcase('delete from ') . $table . $where_sql;
489 if ($options->{returning}) {
490 my ($returning_sql, @returning_bind) = $self->_delete_returning($options);
491 $sql .= $returning_sql;
492 push @bind, @returning_bind;
495 return wantarray ? ($sql, @bind) : $sql;
498 # So that subclasses can override DELETE ... RETURNING separately from
500 sub _delete_returning { shift->_returning(@_) }
504 #======================================================================
506 #======================================================================
510 # Finally, a separate routine just to handle WHERE clauses
512 my ($self, $where, $order) = @_;
515 my ($sql, @bind) = defined($where)
516 ? $self->_recurse_where($where)
518 $sql = (defined $sql and length $sql) ? $self->_sqlcase(' where ') . "( $sql )" : '';
522 my ($order_sql, @order_bind) = $self->_order_by($order);
524 push @bind, @order_bind;
527 return wantarray ? ($sql, @bind) : $sql;
531 my ($self, $expr, $logic) = @_;
532 return undef unless defined($expr);
533 if (ref($expr) eq 'HASH') {
534 if (keys %$expr > 1) {
538 map $self->_expand_expr_hashpair($_ => $expr->{$_}, $logic),
542 return unless %$expr;
543 return $self->_expand_expr_hashpair(%$expr, $logic);
545 if (ref($expr) eq 'ARRAY') {
546 my $logic = lc($logic || $self->{logic});
547 $logic eq 'and' or $logic eq 'or' or puke "unknown logic: $logic";
553 while (my ($el) = splice @expr, 0, 1) {
554 puke "Supplying an empty left hand side argument is not supported in array-pairs"
555 unless defined($el) and length($el);
556 my $elref = ref($el);
558 push(@res, $self->_expand_expr({ $el, shift(@expr) }));
559 } elsif ($elref eq 'ARRAY') {
560 push(@res, $self->_expand_expr($el)) if @$el;
561 } elsif (my $l = is_literal_value($el)) {
562 push @res, { -literal => $l };
563 } elsif ($elref eq 'HASH') {
564 push @res, $self->_expand_expr($el);
569 return { -op => [ $logic, @res ] };
571 if (my $literal = is_literal_value($expr)) {
572 return +{ -literal => $literal };
574 if (!ref($expr) or Scalar::Util::blessed($expr)) {
575 if (my $m = our $Cur_Col_Meta) {
576 return +{ -bind => [ $m, $expr ] };
578 return +{ -value => $expr };
583 sub _expand_expr_hashpair {
584 my ($self, $k, $v, $logic) = @_;
585 unless (defined($k) and length($k)) {
586 if (defined($k) and my $literal = is_literal_value($v)) {
587 belch 'Hash-pairs consisting of an empty string with a literal are deprecated, and will be removed in 2.0: use -and => [ $literal ] instead';
588 return { -literal => $literal };
590 puke "Supplying an empty left hand side argument is not supported";
593 $self->_assert_pass_injection_guard($k =~ /^-(.*)$/s);
594 if ($k =~ s/ [_\s]? \d+ $//x ) {
595 belch 'Use of [and|or|nest]_N modifiers is deprecated and will be removed in SQLA v2.0. '
596 . "You probably wanted ...-and => [ $k => COND1, $k => COND2 ... ]";
599 return $self->_expand_expr($v);
603 return $self->_expand_expr($v);
605 puke "-bool => undef not supported" unless defined($v);
606 return { -ident => $v };
609 return { -op => [ 'not', $self->_expand_expr($v) ] };
611 if (my ($rest) = $k =~/^-not[_ ](.*)$/) {
614 $self->_expand_expr_hashpair("-${rest}", $v, $logic)
617 if (my ($logic) = $k =~ /^-(and|or)$/i) {
618 if (ref($v) eq 'HASH') {
619 return $self->_expand_expr($v, $logic);
621 if (ref($v) eq 'ARRAY') {
622 return $self->_expand_expr($v, $logic);
627 $op =~ s/^-// if length($op) > 1;
629 # top level special ops are illegal in general
630 puke "Illegal use of top-level '-$op'"
631 if !(defined $self->{_nested_func_lhs})
632 and List::Util::first { $op =~ $_->{regex} } @{$self->{special_ops}};
634 if ($k eq '-value' and my $m = our $Cur_Col_Meta) {
635 return +{ -bind => [ $m, $v ] };
637 if ($k eq '-op' or $k eq '-ident' or $k eq '-value' or $k eq '-bind' or $k eq '-literal' or $k eq '-func') {
643 and (keys %$v)[0] =~ /^-/
645 my ($func) = $k =~ /^-(.*)$/;
646 return +{ -func => [ $func, $self->_expand_expr($v) ] };
648 if (!ref($v) or is_literal_value($v)) {
649 return +{ -op => [ $k =~ /^-(.*)$/, $self->_expand_expr($v) ] };
656 and exists $v->{-value}
657 and not defined $v->{-value}
660 return $self->_expand_expr_hashpair($k => { $self->{cmp} => undef });
662 if (!ref($v) or Scalar::Util::blessed($v)) {
667 { -bind => [ $k, $v ] }
671 if (ref($v) eq 'HASH') {
675 map $self->_expand_expr_hashpair($k => { $_ => $v->{$_} }),
682 $self->_assert_pass_injection_guard($vk);
683 if ($vk =~ s/ [_\s]? \d+ $//x ) {
684 belch 'Use of [and|or|nest]_N modifiers is deprecated and will be removed in SQLA v2.0. '
685 . "You probably wanted ...-and => [ -$vk => COND1, -$vk => COND2 ... ]";
687 if ($vk =~ /^(?:not[ _])?between$/) {
688 local our $Cur_Col_Meta = $k;
689 my @rhs = map $self->_expand_expr($_),
690 ref($vv) eq 'ARRAY' ? @$vv : $vv;
692 (@rhs == 1 and ref($rhs[0]) eq 'HASH' and $rhs[0]->{-literal})
694 (@rhs == 2 and defined($rhs[0]) and defined($rhs[1]))
696 puke "Operator '${\uc($vk)}' requires either an arrayref with two defined values or expressions, or a single literal scalarref/arrayref-ref";
699 join(' ', split '_', $vk),
704 if ($vk =~ /^(?:not[ _])?in$/) {
705 if (my $literal = is_literal_value($vv)) {
706 my ($sql, @bind) = @$literal;
707 my $opened_sql = $self->_open_outer_paren($sql);
709 $vk, { -ident => $k },
710 [ { -literal => [ $opened_sql, @bind ] } ]
714 'SQL::Abstract before v1.75 used to generate incorrect SQL when the '
715 . "-${\uc($vk)} operator was given an undef-containing list: !!!AUDIT YOUR CODE "
716 . 'AND DATA!!! (the upcoming Data::Query-based version of SQL::Abstract '
717 . 'will emit the logically correct SQL instead of raising this exception)'
719 puke("Argument passed to the '${\uc($vk)}' operator can not be undefined")
721 my @rhs = map $self->_expand_expr($_),
722 map { ref($_) ? $_ : { -bind => [ $k, $_ ] } }
723 map { defined($_) ? $_: puke($undef_err) }
724 (ref($vv) eq 'ARRAY' ? @$vv : $vv);
725 return $self->${\($vk =~ /^not/ ? 'sqltrue' : 'sqlfalse')} unless @rhs;
728 join(' ', split '_', $vk),
733 if ($vk eq 'ident') {
734 if (! defined $vv or ref $vv) {
735 puke "-$vk requires a single plain scalar argument (a quotable identifier)";
743 if ($vk eq 'value') {
744 return $self->_expand_expr_hashpair($k, undef) unless defined($vv);
748 { -bind => [ $k, $vv ] }
751 if ($vk =~ /^is(?:[ _]not)?$/) {
752 puke "$vk can only take undef as argument"
756 and exists($vv->{-value})
757 and !defined($vv->{-value})
760 return +{ -op => [ $vk.' null', { -ident => $k } ] };
762 if ($vk =~ /^(and|or)$/) {
763 if (ref($vv) eq 'HASH') {
766 map $self->_expand_expr_hashpair($k, { $_ => $vv->{$_} }),
771 if (my $us = List::Util::first { $vk =~ $_->{regex} } @{$self->{user_special_ops}}) {
772 return { -op => [ $vk, { -ident => $k }, $vv ] };
774 if (ref($vv) eq 'ARRAY') {
775 my ($logic, @values) = (
776 (defined($vv->[0]) and $vv->[0] =~ /^-(and|or)$/i)
781 $vk =~ $self->{inequality_op}
782 or join(' ', split '_', $vk) =~ $self->{not_like_op}
784 if (lc($logic) eq '-or' and @values > 1) {
785 my $op = uc join ' ', split '_', $vk;
786 belch "A multi-element arrayref as an argument to the inequality op '$op' "
787 . 'is technically equivalent to an always-true 1=1 (you probably wanted '
788 . "to say ...{ \$inequality_op => [ -and => \@values ] }... instead)"
793 # try to DWIM on equality operators
794 my $op = join ' ', split '_', $vk;
796 $op =~ $self->{equality_op} ? $self->sqlfalse
797 : $op =~ $self->{like_op} ? belch("Supplying an empty arrayref to '@{[ uc $op]}' is deprecated") && $self->sqlfalse
798 : $op =~ $self->{inequality_op} ? $self->sqltrue
799 : $op =~ $self->{not_like_op} ? belch("Supplying an empty arrayref to '@{[ uc $op]}' is deprecated") && $self->sqltrue
800 : puke "operator '$op' applied on an empty array (field '$k')";
804 map $self->_expand_expr_hashpair($k => { $vk => $_ }),
812 and exists $vv->{-value}
813 and not defined $vv->{-value}
816 my $op = join ' ', split '_', $vk;
818 $op =~ /^not$/i ? 'is not' # legacy
819 : $op =~ $self->{equality_op} ? 'is'
820 : $op =~ $self->{like_op} ? belch("Supplying an undefined argument to '@{[ uc $op]}' is deprecated") && 'is'
821 : $op =~ $self->{inequality_op} ? 'is not'
822 : $op =~ $self->{not_like_op} ? belch("Supplying an undefined argument to '@{[ uc $op]}' is deprecated") && 'is not'
823 : puke "unexpected operator '$op' with undef operand";
824 return +{ -op => [ $is.' null', { -ident => $k } ] };
826 local our $Cur_Col_Meta = $k;
830 $self->_expand_expr($vv)
833 if (ref($v) eq 'ARRAY') {
834 return $self->sqlfalse unless @$v;
835 $self->_debug("ARRAY($k) means distribute over elements");
837 $v->[0] =~ /^-((?:and|or))$/i
838 ? ($v = [ @{$v}[1..$#$v] ], $1)
839 : ($self->{logic} || 'or')
843 map $self->_expand_expr({ $k => $_ }, $this_logic), @$v
846 if (my $literal = is_literal_value($v)) {
848 belch 'Hash-pairs consisting of an empty string with a literal are deprecated, and will be removed in 2.0: use -and => [ $literal ] instead';
851 my ($sql, @bind) = @$literal;
852 if ($self->{bindtype} eq 'columns') {
854 if (!defined $_ || ref($_) ne 'ARRAY' || @$_ != 2) {
855 puke "bindtype 'columns' selected, you need to pass: [column_name => bind_value]"
859 return +{ -literal => [ $self->_quote($k).' '.$sql, @bind ] };
865 my ($self, $expr) = @_;
866 my ($k, $v, @rest) = %$expr;
868 my %op = map +("-$_" => '_where_op_'.uc($_)),
869 qw(op func value bind ident literal);
870 if (my $meth = $op{$k}) {
871 return $self->$meth(undef, $v);
873 die "notreached: $k";
877 my ($self, $where, $logic) = @_;
879 #print STDERR Data::Dumper::Concise::Dumper([ $where, $logic ]);
881 my $where_exp = $self->_expand_expr($where, $logic);
883 #print STDERR Data::Dumper::Concise::Dumper([ EXP => $where_exp ]);
885 # dispatch on appropriate method according to refkind of $where
886 # my $method = $self->_METHOD_FOR_refkind("_where", $where_exp);
888 # my ($sql, @bind) = $self->$method($where_exp, $logic);
890 my ($sql, @bind) = defined($where_exp) ? $self->_render_expr($where_exp) : (undef);
892 # DBIx::Class used to call _recurse_where in scalar context
893 # something else might too...
895 return ($sql, @bind);
898 belch "Calling _recurse_where in scalar context is deprecated and will go away before 2.0";
903 sub _where_op_IDENT {
905 my ($op, $rhs) = splice @_, -2;
906 if (! defined $rhs or length ref $rhs) {
907 puke "-$op requires a single plain scalar argument (a quotable identifier)";
910 # in case we are called as a top level special op (no '=')
911 my $has_lhs = my $lhs = shift;
913 $_ = $self->_convert($self->_quote($_)) for ($lhs, $rhs);
921 sub _where_op_VALUE {
922 my ($self, undef, $value) = @_;
924 return ($self->_convert('?'), $self->_bindtype(undef, $value));
927 my %unop_postfix = map +($_ => 1), 'is null', 'is not null';
933 my ($self, $args) = @_;
934 my ($left, $low, $high) = @$args;
935 my ($rhsql, @rhbind) = do {
937 puke "Single arg to between must be a literal"
938 unless $low->{-literal};
941 my ($l, $h) = map [ $self->_render_expr($_) ], $low, $high;
942 (join(' ', $l->[0], $self->_sqlcase('and'), $h->[0]),
943 @{$l}[1..$#$l], @{$h}[1..$#$h])
946 my ($lhsql, @lhbind) = $self->_render_expr($left);
948 join(' ', '(', $lhsql, $self->_sqlcase($op), $rhsql, ')'),
952 }), 'between', 'not between'),
956 my ($self, $args) = @_;
957 my ($lhs, $rhs) = @$args;
960 my ($sql, @bind) = $self->_render_expr($_);
961 push @in_bind, @bind;
964 my ($lhsql, @lbind) = $self->_render_expr($lhs);
966 $lhsql.' '.$self->_sqlcase($op).' ( '
976 my ($self, undef, $v) = @_;
977 my ($op, @args) = @$v;
978 $op =~ s/^-// if length($op) > 1;
980 local $self->{_nested_func_lhs};
981 if (my $h = $special{$op}) {
982 return $self->$h(\@args);
984 if (my $us = List::Util::first { $op =~ $_->{regex} } @{$self->{user_special_ops}}) {
985 puke "Special op '${op}' requires first value to be identifier"
986 unless my ($k) = map $_->{-ident}, grep ref($_) eq 'HASH', $args[0];
987 return $self->${\($us->{handler})}($k, $op, $args[1]);
989 my $final_op = $op =~ /^(?:is|not)_/ ? join(' ', split '_', $op) : $op;
990 if (@args == 1 and $op !~ /^(and|or)$/) {
991 my ($expr_sql, @bind) = $self->_render_expr($args[0]);
992 my $op_sql = $self->_sqlcase($final_op);
994 $unop_postfix{lc($final_op)}
995 ? "${expr_sql} ${op_sql}"
996 : "${op_sql} ${expr_sql}"
998 return (($op eq 'not' ? '('.$final_sql.')' : $final_sql), @bind);
1000 my @parts = map [ $self->_render_expr($_) ], @args;
1001 my ($final_sql) = map +($op =~ /^(and|or)$/ ? "(${_})" : $_), join(
1002 ' '.$self->_sqlcase($final_op).' ',
1007 map @{$_}[1..$#$_], @parts
1013 sub _where_op_FUNC {
1014 my ($self, undef, $rest) = @_;
1015 my ($func, @args) = @$rest;
1019 push @arg_sql, shift @x;
1021 } map [ $self->_render_expr($_) ], @args;
1022 return ($self->_sqlcase($func).'('.join(', ', @arg_sql).')', @bind);
1025 sub _where_op_BIND {
1026 my ($self, undef, $bind) = @_;
1027 return ($self->_convert('?'), $self->_bindtype(@$bind));
1030 sub _where_op_LITERAL {
1031 my ($self, undef, $literal) = @_;
1032 $self->_assert_bindval_matches_bindtype(@{$literal}[1..$#$literal]);
1036 # Some databases (SQLite) treat col IN (1, 2) different from
1037 # col IN ( (1, 2) ). Use this to strip all outer parens while
1038 # adding them back in the corresponding method
1039 sub _open_outer_paren {
1040 my ($self, $sql) = @_;
1042 while (my ($inner) = $sql =~ /^ \s* \( (.*) \) \s* $/xs) {
1044 # there are closing parens inside, need the heavy duty machinery
1045 # to reevaluate the extraction starting from $sql (full reevaluation)
1046 if ($inner =~ /\)/) {
1047 require Text::Balanced;
1049 my (undef, $remainder) = do {
1050 # idiotic design - writes to $@ but *DOES NOT* throw exceptions
1052 Text::Balanced::extract_bracketed($sql, '()', qr/\s*/);
1055 # the entire expression needs to be a balanced bracketed thing
1056 # (after an extract no remainder sans trailing space)
1057 last if defined $remainder and $remainder =~ /\S/;
1067 #======================================================================
1069 #======================================================================
1072 my ($self, $arg) = @_;
1075 for my $c ($self->_order_by_chunks($arg) ) {
1076 $self->_SWITCH_refkind($c, {
1077 SCALAR => sub { push @sql, $c },
1078 ARRAYREF => sub { push @sql, shift @$c; push @bind, @$c },
1084 $self->_sqlcase(' order by'),
1090 return wantarray ? ($sql, @bind) : $sql;
1093 sub _order_by_chunks {
1094 my ($self, $arg) = @_;
1096 return $self->_SWITCH_refkind($arg, {
1099 map { $self->_order_by_chunks($_ ) } @$arg;
1102 ARRAYREFREF => sub {
1103 my ($s, @b) = @$$arg;
1104 $self->_assert_bindval_matches_bindtype(@b);
1108 SCALAR => sub {$self->_quote($arg)},
1110 UNDEF => sub {return () },
1112 SCALARREF => sub {$$arg}, # literal SQL, no quoting
1115 # get first pair in hash
1116 my ($key, $val, @rest) = %$arg;
1118 return () unless $key;
1120 if (@rest or not $key =~ /^-(desc|asc)/i) {
1121 puke "hash passed to _order_by must have exactly one key (-desc or -asc)";
1127 for my $c ($self->_order_by_chunks($val)) {
1130 $self->_SWITCH_refkind($c, {
1135 ($sql, @bind) = @$c;
1139 $sql = $sql . ' ' . $self->_sqlcase($direction);
1141 push @ret, [ $sql, @bind];
1150 #======================================================================
1151 # DATASOURCE (FOR NOW, JUST PLAIN TABLE OR LIST OF TABLES)
1152 #======================================================================
1157 $self->_SWITCH_refkind($from, {
1158 ARRAYREF => sub {join ', ', map { $self->_quote($_) } @$from;},
1159 SCALAR => sub {$self->_quote($from)},
1160 SCALARREF => sub {$$from},
1165 #======================================================================
1167 #======================================================================
1169 # highly optimized, as it's called way too often
1171 # my ($self, $label) = @_;
1173 return '' unless defined $_[1];
1174 return ${$_[1]} if ref($_[1]) eq 'SCALAR';
1176 $_[0]->{quote_char} or
1177 ($_[0]->_assert_pass_injection_guard($_[1]), return $_[1]);
1179 my $qref = ref $_[0]->{quote_char};
1181 !$qref ? ($_[0]->{quote_char}, $_[0]->{quote_char})
1182 : ($qref eq 'ARRAY') ? @{$_[0]->{quote_char}}
1183 : puke "Unsupported quote_char format: $_[0]->{quote_char}";
1185 my $esc = $_[0]->{escape_char} || $r;
1187 # parts containing * are naturally unquoted
1188 return join($_[0]->{name_sep}||'', map
1189 +( $_ eq '*' ? $_ : do { (my $n = $_) =~ s/(\Q$esc\E|\Q$r\E)/$esc$1/g; $l . $n . $r } ),
1190 ( $_[0]->{name_sep} ? split (/\Q$_[0]->{name_sep}\E/, $_[1] ) : $_[1] )
1195 # Conversion, if applicable
1197 #my ($self, $arg) = @_;
1198 if ($_[0]->{convert}) {
1199 return $_[0]->_sqlcase($_[0]->{convert}) .'(' . $_[1] . ')';
1206 #my ($self, $col, @vals) = @_;
1207 # called often - tighten code
1208 return $_[0]->{bindtype} eq 'columns'
1209 ? map {[$_[1], $_]} @_[2 .. $#_]
1214 # Dies if any element of @bind is not in [colname => value] format
1215 # if bindtype is 'columns'.
1216 sub _assert_bindval_matches_bindtype {
1217 # my ($self, @bind) = @_;
1219 if ($self->{bindtype} eq 'columns') {
1221 if (!defined $_ || ref($_) ne 'ARRAY' || @$_ != 2) {
1222 puke "bindtype 'columns' selected, you need to pass: [column_name => bind_value]"
1228 sub _join_sql_clauses {
1229 my ($self, $logic, $clauses_aref, $bind_aref) = @_;
1231 if (@$clauses_aref > 1) {
1232 my $join = " " . $self->_sqlcase($logic) . " ";
1233 my $sql = '( ' . join($join, @$clauses_aref) . ' )';
1234 return ($sql, @$bind_aref);
1236 elsif (@$clauses_aref) {
1237 return ($clauses_aref->[0], @$bind_aref); # no parentheses
1240 return (); # if no SQL, ignore @$bind_aref
1245 # Fix SQL case, if so requested
1247 # LDNOTE: if $self->{case} is true, then it contains 'lower', so we
1248 # don't touch the argument ... crooked logic, but let's not change it!
1249 return $_[0]->{case} ? $_[1] : uc($_[1]);
1253 #======================================================================
1254 # DISPATCHING FROM REFKIND
1255 #======================================================================
1258 my ($self, $data) = @_;
1260 return 'UNDEF' unless defined $data;
1262 # blessed objects are treated like scalars
1263 my $ref = (Scalar::Util::blessed $data) ? '' : ref $data;
1265 return 'SCALAR' unless $ref;
1268 while ($ref eq 'REF') {
1270 $ref = (Scalar::Util::blessed $data) ? '' : ref $data;
1274 return ($ref||'SCALAR') . ('REF' x $n_steps);
1278 my ($self, $data) = @_;
1279 my @try = ($self->_refkind($data));
1280 push @try, 'SCALAR_or_UNDEF' if $try[0] eq 'SCALAR' || $try[0] eq 'UNDEF';
1281 push @try, 'FALLBACK';
1285 sub _METHOD_FOR_refkind {
1286 my ($self, $meth_prefix, $data) = @_;
1289 for (@{$self->_try_refkind($data)}) {
1290 $method = $self->can($meth_prefix."_".$_)
1294 return $method || puke "cannot dispatch on '$meth_prefix' for ".$self->_refkind($data);
1298 sub _SWITCH_refkind {
1299 my ($self, $data, $dispatch_table) = @_;
1302 for (@{$self->_try_refkind($data)}) {
1303 $coderef = $dispatch_table->{$_}
1307 puke "no dispatch entry for ".$self->_refkind($data)
1316 #======================================================================
1317 # VALUES, GENERATE, AUTOLOAD
1318 #======================================================================
1320 # LDNOTE: original code from nwiger, didn't touch code in that section
1321 # I feel the AUTOLOAD stuff should not be the default, it should
1322 # only be activated on explicit demand by user.
1326 my $data = shift || return;
1327 puke "Argument to ", __PACKAGE__, "->values must be a \\%hash"
1328 unless ref $data eq 'HASH';
1331 foreach my $k (sort keys %$data) {
1332 my $v = $data->{$k};
1333 $self->_SWITCH_refkind($v, {
1335 if ($self->{array_datatypes}) { # array datatype
1336 push @all_bind, $self->_bindtype($k, $v);
1338 else { # literal SQL with bind
1339 my ($sql, @bind) = @$v;
1340 $self->_assert_bindval_matches_bindtype(@bind);
1341 push @all_bind, @bind;
1344 ARRAYREFREF => sub { # literal SQL with bind
1345 my ($sql, @bind) = @${$v};
1346 $self->_assert_bindval_matches_bindtype(@bind);
1347 push @all_bind, @bind;
1349 SCALARREF => sub { # literal SQL without bind
1351 SCALAR_or_UNDEF => sub {
1352 push @all_bind, $self->_bindtype($k, $v);
1363 my(@sql, @sqlq, @sqlv);
1367 if ($ref eq 'HASH') {
1368 for my $k (sort keys %$_) {
1371 my $label = $self->_quote($k);
1372 if ($r eq 'ARRAY') {
1373 # literal SQL with bind
1374 my ($sql, @bind) = @$v;
1375 $self->_assert_bindval_matches_bindtype(@bind);
1376 push @sqlq, "$label = $sql";
1378 } elsif ($r eq 'SCALAR') {
1379 # literal SQL without bind
1380 push @sqlq, "$label = $$v";
1382 push @sqlq, "$label = ?";
1383 push @sqlv, $self->_bindtype($k, $v);
1386 push @sql, $self->_sqlcase('set'), join ', ', @sqlq;
1387 } elsif ($ref eq 'ARRAY') {
1388 # unlike insert(), assume these are ONLY the column names, i.e. for SQL
1391 if ($r eq 'ARRAY') { # literal SQL with bind
1392 my ($sql, @bind) = @$v;
1393 $self->_assert_bindval_matches_bindtype(@bind);
1396 } elsif ($r eq 'SCALAR') { # literal SQL without bind
1397 # embedded literal SQL
1404 push @sql, '(' . join(', ', @sqlq) . ')';
1405 } elsif ($ref eq 'SCALAR') {
1409 # strings get case twiddled
1410 push @sql, $self->_sqlcase($_);
1414 my $sql = join ' ', @sql;
1416 # this is pretty tricky
1417 # if ask for an array, return ($stmt, @bind)
1418 # otherwise, s/?/shift @sqlv/ to put it inline
1420 return ($sql, @sqlv);
1422 1 while $sql =~ s/\?/my $d = shift(@sqlv);
1423 ref $d ? $d->[1] : $d/e;
1432 # This allows us to check for a local, then _form, attr
1434 my($name) = $AUTOLOAD =~ /.*::(.+)/;
1435 return $self->generate($name, @_);
1446 SQL::Abstract - Generate SQL from Perl data structures
1452 my $sql = SQL::Abstract->new;
1454 my($stmt, @bind) = $sql->select($source, \@fields, \%where, $order);
1456 my($stmt, @bind) = $sql->insert($table, \%fieldvals || \@values);
1458 my($stmt, @bind) = $sql->update($table, \%fieldvals, \%where);
1460 my($stmt, @bind) = $sql->delete($table, \%where);
1462 # Then, use these in your DBI statements
1463 my $sth = $dbh->prepare($stmt);
1464 $sth->execute(@bind);
1466 # Just generate the WHERE clause
1467 my($stmt, @bind) = $sql->where(\%where, $order);
1469 # Return values in the same order, for hashed queries
1470 # See PERFORMANCE section for more details
1471 my @bind = $sql->values(\%fieldvals);
1475 This module was inspired by the excellent L<DBIx::Abstract>.
1476 However, in using that module I found that what I really wanted
1477 to do was generate SQL, but still retain complete control over my
1478 statement handles and use the DBI interface. So, I set out to
1479 create an abstract SQL generation module.
1481 While based on the concepts used by L<DBIx::Abstract>, there are
1482 several important differences, especially when it comes to WHERE
1483 clauses. I have modified the concepts used to make the SQL easier
1484 to generate from Perl data structures and, IMO, more intuitive.
1485 The underlying idea is for this module to do what you mean, based
1486 on the data structures you provide it. The big advantage is that
1487 you don't have to modify your code every time your data changes,
1488 as this module figures it out.
1490 To begin with, an SQL INSERT is as easy as just specifying a hash
1491 of C<key=value> pairs:
1494 name => 'Jimbo Bobson',
1495 phone => '123-456-7890',
1496 address => '42 Sister Lane',
1497 city => 'St. Louis',
1498 state => 'Louisiana',
1501 The SQL can then be generated with this:
1503 my($stmt, @bind) = $sql->insert('people', \%data);
1505 Which would give you something like this:
1507 $stmt = "INSERT INTO people
1508 (address, city, name, phone, state)
1509 VALUES (?, ?, ?, ?, ?)";
1510 @bind = ('42 Sister Lane', 'St. Louis', 'Jimbo Bobson',
1511 '123-456-7890', 'Louisiana');
1513 These are then used directly in your DBI code:
1515 my $sth = $dbh->prepare($stmt);
1516 $sth->execute(@bind);
1518 =head2 Inserting and Updating Arrays
1520 If your database has array types (like for example Postgres),
1521 activate the special option C<< array_datatypes => 1 >>
1522 when creating the C<SQL::Abstract> object.
1523 Then you may use an arrayref to insert and update database array types:
1525 my $sql = SQL::Abstract->new(array_datatypes => 1);
1527 planets => [qw/Mercury Venus Earth Mars/]
1530 my($stmt, @bind) = $sql->insert('solar_system', \%data);
1534 $stmt = "INSERT INTO solar_system (planets) VALUES (?)"
1536 @bind = (['Mercury', 'Venus', 'Earth', 'Mars']);
1539 =head2 Inserting and Updating SQL
1541 In order to apply SQL functions to elements of your C<%data> you may
1542 specify a reference to an arrayref for the given hash value. For example,
1543 if you need to execute the Oracle C<to_date> function on a value, you can
1544 say something like this:
1548 date_entered => \[ "to_date(?,'MM/DD/YYYY')", "03/02/2003" ],
1551 The first value in the array is the actual SQL. Any other values are
1552 optional and would be included in the bind values array. This gives
1555 my($stmt, @bind) = $sql->insert('people', \%data);
1557 $stmt = "INSERT INTO people (name, date_entered)
1558 VALUES (?, to_date(?,'MM/DD/YYYY'))";
1559 @bind = ('Bill', '03/02/2003');
1561 An UPDATE is just as easy, all you change is the name of the function:
1563 my($stmt, @bind) = $sql->update('people', \%data);
1565 Notice that your C<%data> isn't touched; the module will generate
1566 the appropriately quirky SQL for you automatically. Usually you'll
1567 want to specify a WHERE clause for your UPDATE, though, which is
1568 where handling C<%where> hashes comes in handy...
1570 =head2 Complex where statements
1572 This module can generate pretty complicated WHERE statements
1573 easily. For example, simple C<key=value> pairs are taken to mean
1574 equality, and if you want to see if a field is within a set
1575 of values, you can use an arrayref. Let's say we wanted to
1576 SELECT some data based on this criteria:
1579 requestor => 'inna',
1580 worker => ['nwiger', 'rcwe', 'sfz'],
1581 status => { '!=', 'completed' }
1584 my($stmt, @bind) = $sql->select('tickets', '*', \%where);
1586 The above would give you something like this:
1588 $stmt = "SELECT * FROM tickets WHERE
1589 ( requestor = ? ) AND ( status != ? )
1590 AND ( worker = ? OR worker = ? OR worker = ? )";
1591 @bind = ('inna', 'completed', 'nwiger', 'rcwe', 'sfz');
1593 Which you could then use in DBI code like so:
1595 my $sth = $dbh->prepare($stmt);
1596 $sth->execute(@bind);
1602 The methods are simple. There's one for every major SQL operation,
1603 and a constructor you use first. The arguments are specified in a
1604 similar order for each method (table, then fields, then a where
1605 clause) to try and simplify things.
1607 =head2 new(option => 'value')
1609 The C<new()> function takes a list of options and values, and returns
1610 a new B<SQL::Abstract> object which can then be used to generate SQL
1611 through the methods below. The options accepted are:
1617 If set to 'lower', then SQL will be generated in all lowercase. By
1618 default SQL is generated in "textbook" case meaning something like:
1620 SELECT a_field FROM a_table WHERE some_field LIKE '%someval%'
1622 Any setting other than 'lower' is ignored.
1626 This determines what the default comparison operator is. By default
1627 it is C<=>, meaning that a hash like this:
1629 %where = (name => 'nwiger', email => 'nate@wiger.org');
1631 Will generate SQL like this:
1633 WHERE name = 'nwiger' AND email = 'nate@wiger.org'
1635 However, you may want loose comparisons by default, so if you set
1636 C<cmp> to C<like> you would get SQL such as:
1638 WHERE name like 'nwiger' AND email like 'nate@wiger.org'
1640 You can also override the comparison on an individual basis - see
1641 the huge section on L</"WHERE CLAUSES"> at the bottom.
1643 =item sqltrue, sqlfalse
1645 Expressions for inserting boolean values within SQL statements.
1646 By default these are C<1=1> and C<1=0>. They are used
1647 by the special operators C<-in> and C<-not_in> for generating
1648 correct SQL even when the argument is an empty array (see below).
1652 This determines the default logical operator for multiple WHERE
1653 statements in arrays or hashes. If absent, the default logic is "or"
1654 for arrays, and "and" for hashes. This means that a WHERE
1658 event_date => {'>=', '2/13/99'},
1659 event_date => {'<=', '4/24/03'},
1662 will generate SQL like this:
1664 WHERE event_date >= '2/13/99' OR event_date <= '4/24/03'
1666 This is probably not what you want given this query, though (look
1667 at the dates). To change the "OR" to an "AND", simply specify:
1669 my $sql = SQL::Abstract->new(logic => 'and');
1671 Which will change the above C<WHERE> to:
1673 WHERE event_date >= '2/13/99' AND event_date <= '4/24/03'
1675 The logic can also be changed locally by inserting
1676 a modifier in front of an arrayref:
1678 @where = (-and => [event_date => {'>=', '2/13/99'},
1679 event_date => {'<=', '4/24/03'} ]);
1681 See the L</"WHERE CLAUSES"> section for explanations.
1685 This will automatically convert comparisons using the specified SQL
1686 function for both column and value. This is mostly used with an argument
1687 of C<upper> or C<lower>, so that the SQL will have the effect of
1688 case-insensitive "searches". For example, this:
1690 $sql = SQL::Abstract->new(convert => 'upper');
1691 %where = (keywords => 'MaKe iT CAse inSeNSItive');
1693 Will turn out the following SQL:
1695 WHERE upper(keywords) like upper('MaKe iT CAse inSeNSItive')
1697 The conversion can be C<upper()>, C<lower()>, or any other SQL function
1698 that can be applied symmetrically to fields (actually B<SQL::Abstract> does
1699 not validate this option; it will just pass through what you specify verbatim).
1703 This is a kludge because many databases suck. For example, you can't
1704 just bind values using DBI's C<execute()> for Oracle C<CLOB> or C<BLOB> fields.
1705 Instead, you have to use C<bind_param()>:
1707 $sth->bind_param(1, 'reg data');
1708 $sth->bind_param(2, $lots, {ora_type => ORA_CLOB});
1710 The problem is, B<SQL::Abstract> will normally just return a C<@bind> array,
1711 which loses track of which field each slot refers to. Fear not.
1713 If you specify C<bindtype> in new, you can determine how C<@bind> is returned.
1714 Currently, you can specify either C<normal> (default) or C<columns>. If you
1715 specify C<columns>, you will get an array that looks like this:
1717 my $sql = SQL::Abstract->new(bindtype => 'columns');
1718 my($stmt, @bind) = $sql->insert(...);
1721 [ 'column1', 'value1' ],
1722 [ 'column2', 'value2' ],
1723 [ 'column3', 'value3' ],
1726 You can then iterate through this manually, using DBI's C<bind_param()>.
1728 $sth->prepare($stmt);
1731 my($col, $data) = @$_;
1732 if ($col eq 'details' || $col eq 'comments') {
1733 $sth->bind_param($i, $data, {ora_type => ORA_CLOB});
1734 } elsif ($col eq 'image') {
1735 $sth->bind_param($i, $data, {ora_type => ORA_BLOB});
1737 $sth->bind_param($i, $data);
1741 $sth->execute; # execute without @bind now
1743 Now, why would you still use B<SQL::Abstract> if you have to do this crap?
1744 Basically, the advantage is still that you don't have to care which fields
1745 are or are not included. You could wrap that above C<for> loop in a simple
1746 sub called C<bind_fields()> or something and reuse it repeatedly. You still
1747 get a layer of abstraction over manual SQL specification.
1749 Note that if you set L</bindtype> to C<columns>, the C<\[ $sql, @bind ]>
1750 construct (see L</Literal SQL with placeholders and bind values (subqueries)>)
1751 will expect the bind values in this format.
1755 This is the character that a table or column name will be quoted
1756 with. By default this is an empty string, but you could set it to
1757 the character C<`>, to generate SQL like this:
1759 SELECT `a_field` FROM `a_table` WHERE `some_field` LIKE '%someval%'
1761 Alternatively, you can supply an array ref of two items, the first being the left
1762 hand quote character, and the second the right hand quote character. For
1763 example, you could supply C<['[',']']> for SQL Server 2000 compliant quotes
1764 that generates SQL like this:
1766 SELECT [a_field] FROM [a_table] WHERE [some_field] LIKE '%someval%'
1768 Quoting is useful if you have tables or columns names that are reserved
1769 words in your database's SQL dialect.
1773 This is the character that will be used to escape L</quote_char>s appearing
1774 in an identifier before it has been quoted.
1776 The parameter default in case of a single L</quote_char> character is the quote
1779 When opening-closing-style quoting is used (L</quote_char> is an arrayref)
1780 this parameter defaults to the B<closing (right)> L</quote_char>. Occurrences
1781 of the B<opening (left)> L</quote_char> within the identifier are currently left
1782 untouched. The default for opening-closing-style quotes may change in future
1783 versions, thus you are B<strongly encouraged> to specify the escape character
1788 This is the character that separates a table and column name. It is
1789 necessary to specify this when the C<quote_char> option is selected,
1790 so that tables and column names can be individually quoted like this:
1792 SELECT `table`.`one_field` FROM `table` WHERE `table`.`other_field` = 1
1794 =item injection_guard
1796 A regular expression C<qr/.../> that is applied to any C<-function> and unquoted
1797 column name specified in a query structure. This is a safety mechanism to avoid
1798 injection attacks when mishandling user input e.g.:
1800 my %condition_as_column_value_pairs = get_values_from_user();
1801 $sqla->select( ... , \%condition_as_column_value_pairs );
1803 If the expression matches an exception is thrown. Note that literal SQL
1804 supplied via C<\'...'> or C<\['...']> is B<not> checked in any way.
1806 Defaults to checking for C<;> and the C<GO> keyword (TransactSQL)
1808 =item array_datatypes
1810 When this option is true, arrayrefs in INSERT or UPDATE are
1811 interpreted as array datatypes and are passed directly
1813 When this option is false, arrayrefs are interpreted
1814 as literal SQL, just like refs to arrayrefs
1815 (but this behavior is for backwards compatibility; when writing
1816 new queries, use the "reference to arrayref" syntax
1822 Takes a reference to a list of "special operators"
1823 to extend the syntax understood by L<SQL::Abstract>.
1824 See section L</"SPECIAL OPERATORS"> for details.
1828 Takes a reference to a list of "unary operators"
1829 to extend the syntax understood by L<SQL::Abstract>.
1830 See section L</"UNARY OPERATORS"> for details.
1836 =head2 insert($table, \@values || \%fieldvals, \%options)
1838 This is the simplest function. You simply give it a table name
1839 and either an arrayref of values or hashref of field/value pairs.
1840 It returns an SQL INSERT statement and a list of bind values.
1841 See the sections on L</"Inserting and Updating Arrays"> and
1842 L</"Inserting and Updating SQL"> for information on how to insert
1843 with those data types.
1845 The optional C<\%options> hash reference may contain additional
1846 options to generate the insert SQL. Currently supported options
1853 Takes either a scalar of raw SQL fields, or an array reference of
1854 field names, and adds on an SQL C<RETURNING> statement at the end.
1855 This allows you to return data generated by the insert statement
1856 (such as row IDs) without performing another C<SELECT> statement.
1857 Note, however, this is not part of the SQL standard and may not
1858 be supported by all database engines.
1862 =head2 update($table, \%fieldvals, \%where, \%options)
1864 This takes a table, hashref of field/value pairs, and an optional
1865 hashref L<WHERE clause|/WHERE CLAUSES>. It returns an SQL UPDATE function and a list
1867 See the sections on L</"Inserting and Updating Arrays"> and
1868 L</"Inserting and Updating SQL"> for information on how to insert
1869 with those data types.
1871 The optional C<\%options> hash reference may contain additional
1872 options to generate the update SQL. Currently supported options
1879 See the C<returning> option to
1880 L<insert|/insert($table, \@values || \%fieldvals, \%options)>.
1884 =head2 select($source, $fields, $where, $order)
1886 This returns a SQL SELECT statement and associated list of bind values, as
1887 specified by the arguments:
1893 Specification of the 'FROM' part of the statement.
1894 The argument can be either a plain scalar (interpreted as a table
1895 name, will be quoted), or an arrayref (interpreted as a list
1896 of table names, joined by commas, quoted), or a scalarref
1897 (literal SQL, not quoted).
1901 Specification of the list of fields to retrieve from
1903 The argument can be either an arrayref (interpreted as a list
1904 of field names, will be joined by commas and quoted), or a
1905 plain scalar (literal SQL, not quoted).
1906 Please observe that this API is not as flexible as that of
1907 the first argument C<$source>, for backwards compatibility reasons.
1911 Optional argument to specify the WHERE part of the query.
1912 The argument is most often a hashref, but can also be
1913 an arrayref or plain scalar --
1914 see section L<WHERE clause|/"WHERE CLAUSES"> for details.
1918 Optional argument to specify the ORDER BY part of the query.
1919 The argument can be a scalar, a hashref or an arrayref
1920 -- see section L<ORDER BY clause|/"ORDER BY CLAUSES">
1926 =head2 delete($table, \%where, \%options)
1928 This takes a table name and optional hashref L<WHERE clause|/WHERE CLAUSES>.
1929 It returns an SQL DELETE statement and list of bind values.
1931 The optional C<\%options> hash reference may contain additional
1932 options to generate the delete SQL. Currently supported options
1939 See the C<returning> option to
1940 L<insert|/insert($table, \@values || \%fieldvals, \%options)>.
1944 =head2 where(\%where, $order)
1946 This is used to generate just the WHERE clause. For example,
1947 if you have an arbitrary data structure and know what the
1948 rest of your SQL is going to look like, but want an easy way
1949 to produce a WHERE clause, use this. It returns an SQL WHERE
1950 clause and list of bind values.
1953 =head2 values(\%data)
1955 This just returns the values from the hash C<%data>, in the same
1956 order that would be returned from any of the other above queries.
1957 Using this allows you to markedly speed up your queries if you
1958 are affecting lots of rows. See below under the L</"PERFORMANCE"> section.
1960 =head2 generate($any, 'number', $of, \@data, $struct, \%types)
1962 Warning: This is an experimental method and subject to change.
1964 This returns arbitrarily generated SQL. It's a really basic shortcut.
1965 It will return two different things, depending on return context:
1967 my($stmt, @bind) = $sql->generate('create table', \$table, \@fields);
1968 my $stmt_and_val = $sql->generate('create table', \$table, \@fields);
1970 These would return the following:
1972 # First calling form
1973 $stmt = "CREATE TABLE test (?, ?)";
1974 @bind = (field1, field2);
1976 # Second calling form
1977 $stmt_and_val = "CREATE TABLE test (field1, field2)";
1979 Depending on what you're trying to do, it's up to you to choose the correct
1980 format. In this example, the second form is what you would want.
1984 $sql->generate('alter session', { nls_date_format => 'MM/YY' });
1988 ALTER SESSION SET nls_date_format = 'MM/YY'
1990 You get the idea. Strings get their case twiddled, but everything
1991 else remains verbatim.
1993 =head1 EXPORTABLE FUNCTIONS
1995 =head2 is_plain_value
1997 Determines if the supplied argument is a plain value as understood by this
2002 =item * The value is C<undef>
2004 =item * The value is a non-reference
2006 =item * The value is an object with stringification overloading
2008 =item * The value is of the form C<< { -value => $anything } >>
2012 On failure returns C<undef>, on success returns a B<scalar> reference
2013 to the original supplied argument.
2019 The stringification overloading detection is rather advanced: it takes
2020 into consideration not only the presence of a C<""> overload, but if that
2021 fails also checks for enabled
2022 L<autogenerated versions of C<"">|overload/Magic Autogeneration>, based
2023 on either C<0+> or C<bool>.
2025 Unfortunately testing in the field indicates that this
2026 detection B<< may tickle a latent bug in perl versions before 5.018 >>,
2027 but only when very large numbers of stringifying objects are involved.
2028 At the time of writing ( Sep 2014 ) there is no clear explanation of
2029 the direct cause, nor is there a manageably small test case that reliably
2030 reproduces the problem.
2032 If you encounter any of the following exceptions in B<random places within
2033 your application stack> - this module may be to blame:
2035 Operation "ne": no method found,
2036 left argument in overloaded package <something>,
2037 right argument in overloaded package <something>
2041 Stub found while resolving method "???" overloading """" in package <something>
2043 If you fall victim to the above - please attempt to reduce the problem
2044 to something that could be sent to the L<SQL::Abstract developers
2045 |DBIx::Class/GETTING HELP/SUPPORT>
2046 (either publicly or privately). As a workaround in the meantime you can
2047 set C<$ENV{SQLA_ISVALUE_IGNORE_AUTOGENERATED_STRINGIFICATION}> to a true
2048 value, which will most likely eliminate your problem (at the expense of
2049 not being able to properly detect exotic forms of stringification).
2051 This notice and environment variable will be removed in a future version,
2052 as soon as the underlying problem is found and a reliable workaround is
2057 =head2 is_literal_value
2059 Determines if the supplied argument is a literal value as understood by this
2064 =item * C<\$sql_string>
2066 =item * C<\[ $sql_string, @bind_values ]>
2070 On failure returns C<undef>, on success returns an B<array> reference
2071 containing the unpacked version of the supplied literal SQL and bind values.
2073 =head1 WHERE CLAUSES
2077 This module uses a variation on the idea from L<DBIx::Abstract>. It
2078 is B<NOT>, repeat I<not> 100% compatible. B<The main logic of this
2079 module is that things in arrays are OR'ed, and things in hashes
2082 The easiest way to explain is to show lots of examples. After
2083 each C<%where> hash shown, it is assumed you used:
2085 my($stmt, @bind) = $sql->where(\%where);
2087 However, note that the C<%where> hash can be used directly in any
2088 of the other functions as well, as described above.
2090 =head2 Key-value pairs
2092 So, let's get started. To begin, a simple hash:
2096 status => 'completed'
2099 Is converted to SQL C<key = val> statements:
2101 $stmt = "WHERE user = ? AND status = ?";
2102 @bind = ('nwiger', 'completed');
2104 One common thing I end up doing is having a list of values that
2105 a field can be in. To do this, simply specify a list inside of
2110 status => ['assigned', 'in-progress', 'pending'];
2113 This simple code will create the following:
2115 $stmt = "WHERE user = ? AND ( status = ? OR status = ? OR status = ? )";
2116 @bind = ('nwiger', 'assigned', 'in-progress', 'pending');
2118 A field associated to an empty arrayref will be considered a
2119 logical false and will generate 0=1.
2121 =head2 Tests for NULL values
2123 If the value part is C<undef> then this is converted to SQL <IS NULL>
2132 $stmt = "WHERE user = ? AND status IS NULL";
2135 To test if a column IS NOT NULL:
2139 status => { '!=', undef },
2142 =head2 Specific comparison operators
2144 If you want to specify a different type of operator for your comparison,
2145 you can use a hashref for a given column:
2149 status => { '!=', 'completed' }
2152 Which would generate:
2154 $stmt = "WHERE user = ? AND status != ?";
2155 @bind = ('nwiger', 'completed');
2157 To test against multiple values, just enclose the values in an arrayref:
2159 status => { '=', ['assigned', 'in-progress', 'pending'] };
2161 Which would give you:
2163 "WHERE status = ? OR status = ? OR status = ?"
2166 The hashref can also contain multiple pairs, in which case it is expanded
2167 into an C<AND> of its elements:
2171 status => { '!=', 'completed', -not_like => 'pending%' }
2174 # Or more dynamically, like from a form
2175 $where{user} = 'nwiger';
2176 $where{status}{'!='} = 'completed';
2177 $where{status}{'-not_like'} = 'pending%';
2179 # Both generate this
2180 $stmt = "WHERE user = ? AND status != ? AND status NOT LIKE ?";
2181 @bind = ('nwiger', 'completed', 'pending%');
2184 To get an OR instead, you can combine it with the arrayref idea:
2188 priority => [ { '=', 2 }, { '>', 5 } ]
2191 Which would generate:
2193 $stmt = "WHERE ( priority = ? OR priority > ? ) AND user = ?";
2194 @bind = ('2', '5', 'nwiger');
2196 If you want to include literal SQL (with or without bind values), just use a
2197 scalar reference or reference to an arrayref as the value:
2200 date_entered => { '>' => \["to_date(?, 'MM/DD/YYYY')", "11/26/2008"] },
2201 date_expires => { '<' => \"now()" }
2204 Which would generate:
2206 $stmt = "WHERE date_entered > to_date(?, 'MM/DD/YYYY') AND date_expires < now()";
2207 @bind = ('11/26/2008');
2210 =head2 Logic and nesting operators
2212 In the example above,
2213 there is a subtle trap if you want to say something like
2214 this (notice the C<AND>):
2216 WHERE priority != ? AND priority != ?
2218 Because, in Perl you I<can't> do this:
2220 priority => { '!=' => 2, '!=' => 1 }
2222 As the second C<!=> key will obliterate the first. The solution
2223 is to use the special C<-modifier> form inside an arrayref:
2225 priority => [ -and => {'!=', 2},
2229 Normally, these would be joined by C<OR>, but the modifier tells it
2230 to use C<AND> instead. (Hint: You can use this in conjunction with the
2231 C<logic> option to C<new()> in order to change the way your queries
2232 work by default.) B<Important:> Note that the C<-modifier> goes
2233 B<INSIDE> the arrayref, as an extra first element. This will
2234 B<NOT> do what you think it might:
2236 priority => -and => [{'!=', 2}, {'!=', 1}] # WRONG!
2238 Here is a quick list of equivalencies, since there is some overlap:
2241 status => {'!=', 'completed', 'not like', 'pending%' }
2242 status => [ -and => {'!=', 'completed'}, {'not like', 'pending%'}]
2245 status => {'=', ['assigned', 'in-progress']}
2246 status => [ -or => {'=', 'assigned'}, {'=', 'in-progress'}]
2247 status => [ {'=', 'assigned'}, {'=', 'in-progress'} ]
2251 =head2 Special operators: IN, BETWEEN, etc.
2253 You can also use the hashref format to compare a list of fields using the
2254 C<IN> comparison operator, by specifying the list as an arrayref:
2257 status => 'completed',
2258 reportid => { -in => [567, 2335, 2] }
2261 Which would generate:
2263 $stmt = "WHERE status = ? AND reportid IN (?,?,?)";
2264 @bind = ('completed', '567', '2335', '2');
2266 The reverse operator C<-not_in> generates SQL C<NOT IN> and is used in
2269 If the argument to C<-in> is an empty array, 'sqlfalse' is generated
2270 (by default: C<1=0>). Similarly, C<< -not_in => [] >> generates
2271 'sqltrue' (by default: C<1=1>).
2273 In addition to the array you can supply a chunk of literal sql or
2274 literal sql with bind:
2277 customer => { -in => \[
2278 'SELECT cust_id FROM cust WHERE balance > ?',
2281 status => { -in => \'SELECT status_codes FROM states' },
2287 customer IN ( SELECT cust_id FROM cust WHERE balance > ? )
2288 AND status IN ( SELECT status_codes FROM states )
2292 Finally, if the argument to C<-in> is not a reference, it will be
2293 treated as a single-element array.
2295 Another pair of operators is C<-between> and C<-not_between>,
2296 used with an arrayref of two values:
2300 completion_date => {
2301 -not_between => ['2002-10-01', '2003-02-06']
2307 WHERE user = ? AND completion_date NOT BETWEEN ( ? AND ? )
2309 Just like with C<-in> all plausible combinations of literal SQL
2313 start0 => { -between => [ 1, 2 ] },
2314 start1 => { -between => \["? AND ?", 1, 2] },
2315 start2 => { -between => \"lower(x) AND upper(y)" },
2316 start3 => { -between => [
2318 \["upper(?)", 'stuff' ],
2325 ( start0 BETWEEN ? AND ? )
2326 AND ( start1 BETWEEN ? AND ? )
2327 AND ( start2 BETWEEN lower(x) AND upper(y) )
2328 AND ( start3 BETWEEN lower(x) AND upper(?) )
2330 @bind = (1, 2, 1, 2, 'stuff');
2333 These are the two builtin "special operators"; but the
2334 list can be expanded: see section L</"SPECIAL OPERATORS"> below.
2336 =head2 Unary operators: bool
2338 If you wish to test against boolean columns or functions within your
2339 database you can use the C<-bool> and C<-not_bool> operators. For
2340 example to test the column C<is_user> being true and the column
2341 C<is_enabled> being false you would use:-
2345 -not_bool => 'is_enabled',
2350 WHERE is_user AND NOT is_enabled
2352 If a more complex combination is required, testing more conditions,
2353 then you should use the and/or operators:-
2358 -not_bool => { two=> { -rlike => 'bar' } },
2359 -not_bool => { three => [ { '=', 2 }, { '>', 5 } ] },
2370 (NOT ( three = ? OR three > ? ))
2373 =head2 Nested conditions, -and/-or prefixes
2375 So far, we've seen how multiple conditions are joined with a top-level
2376 C<AND>. We can change this by putting the different conditions we want in
2377 hashes and then putting those hashes in an array. For example:
2382 status => { -like => ['pending%', 'dispatched'] },
2386 status => 'unassigned',
2390 This data structure would create the following:
2392 $stmt = "WHERE ( user = ? AND ( status LIKE ? OR status LIKE ? ) )
2393 OR ( user = ? AND status = ? ) )";
2394 @bind = ('nwiger', 'pending', 'dispatched', 'robot', 'unassigned');
2397 Clauses in hashrefs or arrayrefs can be prefixed with an C<-and> or C<-or>
2398 to change the logic inside:
2404 -and => [ workhrs => {'>', 20}, geo => 'ASIA' ],
2405 -or => { workhrs => {'<', 50}, geo => 'EURO' },
2412 $stmt = "WHERE ( user = ?
2413 AND ( ( workhrs > ? AND geo = ? )
2414 OR ( workhrs < ? OR geo = ? ) ) )";
2415 @bind = ('nwiger', '20', 'ASIA', '50', 'EURO');
2417 =head3 Algebraic inconsistency, for historical reasons
2419 C<Important note>: when connecting several conditions, the C<-and->|C<-or>
2420 operator goes C<outside> of the nested structure; whereas when connecting
2421 several constraints on one column, the C<-and> operator goes
2422 C<inside> the arrayref. Here is an example combining both features:
2425 -and => [a => 1, b => 2],
2426 -or => [c => 3, d => 4],
2427 e => [-and => {-like => 'foo%'}, {-like => '%bar'} ]
2432 WHERE ( ( ( a = ? AND b = ? )
2433 OR ( c = ? OR d = ? )
2434 OR ( e LIKE ? AND e LIKE ? ) ) )
2436 This difference in syntax is unfortunate but must be preserved for
2437 historical reasons. So be careful: the two examples below would
2438 seem algebraically equivalent, but they are not
2441 { -like => 'foo%' },
2442 { -like => '%bar' },
2444 # yields: WHERE ( ( col LIKE ? AND col LIKE ? ) )
2447 { col => { -like => 'foo%' } },
2448 { col => { -like => '%bar' } },
2450 # yields: WHERE ( ( col LIKE ? OR col LIKE ? ) )
2453 =head2 Literal SQL and value type operators
2455 The basic premise of SQL::Abstract is that in WHERE specifications the "left
2456 side" is a column name and the "right side" is a value (normally rendered as
2457 a placeholder). This holds true for both hashrefs and arrayref pairs as you
2458 see in the L</WHERE CLAUSES> examples above. Sometimes it is necessary to
2459 alter this behavior. There are several ways of doing so.
2463 This is a virtual operator that signals the string to its right side is an
2464 identifier (a column name) and not a value. For example to compare two
2465 columns you would write:
2468 priority => { '<', 2 },
2469 requestor => { -ident => 'submitter' },
2474 $stmt = "WHERE priority < ? AND requestor = submitter";
2477 If you are maintaining legacy code you may see a different construct as
2478 described in L</Deprecated usage of Literal SQL>, please use C<-ident> in new
2483 This is a virtual operator that signals that the construct to its right side
2484 is a value to be passed to DBI. This is for example necessary when you want
2485 to write a where clause against an array (for RDBMS that support such
2486 datatypes). For example:
2489 array => { -value => [1, 2, 3] }
2494 $stmt = 'WHERE array = ?';
2495 @bind = ([1, 2, 3]);
2497 Note that if you were to simply say:
2503 the result would probably not be what you wanted:
2505 $stmt = 'WHERE array = ? OR array = ? OR array = ?';
2510 Finally, sometimes only literal SQL will do. To include a random snippet
2511 of SQL verbatim, you specify it as a scalar reference. Consider this only
2512 as a last resort. Usually there is a better way. For example:
2515 priority => { '<', 2 },
2516 requestor => { -in => \'(SELECT name FROM hitmen)' },
2521 $stmt = "WHERE priority < ? AND requestor IN (SELECT name FROM hitmen)"
2524 Note that in this example, you only get one bind parameter back, since
2525 the verbatim SQL is passed as part of the statement.
2529 Never use untrusted input as a literal SQL argument - this is a massive
2530 security risk (there is no way to check literal snippets for SQL
2531 injections and other nastyness). If you need to deal with untrusted input
2532 use literal SQL with placeholders as described next.
2534 =head3 Literal SQL with placeholders and bind values (subqueries)
2536 If the literal SQL to be inserted has placeholders and bind values,
2537 use a reference to an arrayref (yes this is a double reference --
2538 not so common, but perfectly legal Perl). For example, to find a date
2539 in Postgres you can use something like this:
2542 date_column => \[ "= date '2008-09-30' - ?::integer", 10 ]
2547 $stmt = "WHERE ( date_column = date '2008-09-30' - ?::integer )"
2550 Note that you must pass the bind values in the same format as they are returned
2551 by L<where|/where(\%where, $order)>. This means that if you set L</bindtype>
2552 to C<columns>, you must provide the bind values in the
2553 C<< [ column_meta => value ] >> format, where C<column_meta> is an opaque
2554 scalar value; most commonly the column name, but you can use any scalar value
2555 (including references and blessed references), L<SQL::Abstract> will simply
2556 pass it through intact. So if C<bindtype> is set to C<columns> the above
2557 example will look like:
2560 date_column => \[ "= date '2008-09-30' - ?::integer", [ {} => 10 ] ]
2563 Literal SQL is especially useful for nesting parenthesized clauses in the
2564 main SQL query. Here is a first example:
2566 my ($sub_stmt, @sub_bind) = ("SELECT c1 FROM t1 WHERE c2 < ? AND c3 LIKE ?",
2570 bar => \["IN ($sub_stmt)" => @sub_bind],
2575 $stmt = "WHERE (foo = ? AND bar IN (SELECT c1 FROM t1
2576 WHERE c2 < ? AND c3 LIKE ?))";
2577 @bind = (1234, 100, "foo%");
2579 Other subquery operators, like for example C<"E<gt> ALL"> or C<"NOT IN">,
2580 are expressed in the same way. Of course the C<$sub_stmt> and
2581 its associated bind values can be generated through a former call
2584 my ($sub_stmt, @sub_bind)
2585 = $sql->select("t1", "c1", {c2 => {"<" => 100},
2586 c3 => {-like => "foo%"}});
2589 bar => \["> ALL ($sub_stmt)" => @sub_bind],
2592 In the examples above, the subquery was used as an operator on a column;
2593 but the same principle also applies for a clause within the main C<%where>
2594 hash, like an EXISTS subquery:
2596 my ($sub_stmt, @sub_bind)
2597 = $sql->select("t1", "*", {c1 => 1, c2 => \"> t0.c0"});
2598 my %where = ( -and => [
2600 \["EXISTS ($sub_stmt)" => @sub_bind],
2605 $stmt = "WHERE (foo = ? AND EXISTS (SELECT * FROM t1
2606 WHERE c1 = ? AND c2 > t0.c0))";
2610 Observe that the condition on C<c2> in the subquery refers to
2611 column C<t0.c0> of the main query: this is I<not> a bind
2612 value, so we have to express it through a scalar ref.
2613 Writing C<< c2 => {">" => "t0.c0"} >> would have generated
2614 C<< c2 > ? >> with bind value C<"t0.c0"> ... not exactly
2615 what we wanted here.
2617 Finally, here is an example where a subquery is used
2618 for expressing unary negation:
2620 my ($sub_stmt, @sub_bind)
2621 = $sql->where({age => [{"<" => 10}, {">" => 20}]});
2622 $sub_stmt =~ s/^ where //i; # don't want "WHERE" in the subclause
2624 lname => {like => '%son%'},
2625 \["NOT ($sub_stmt)" => @sub_bind],
2630 $stmt = "lname LIKE ? AND NOT ( age < ? OR age > ? )"
2631 @bind = ('%son%', 10, 20)
2633 =head3 Deprecated usage of Literal SQL
2635 Below are some examples of archaic use of literal SQL. It is shown only as
2636 reference for those who deal with legacy code. Each example has a much
2637 better, cleaner and safer alternative that users should opt for in new code.
2643 my %where = ( requestor => \'IS NOT NULL' )
2645 $stmt = "WHERE requestor IS NOT NULL"
2647 This used to be the way of generating NULL comparisons, before the handling
2648 of C<undef> got formalized. For new code please use the superior syntax as
2649 described in L</Tests for NULL values>.
2653 my %where = ( requestor => \'= submitter' )
2655 $stmt = "WHERE requestor = submitter"
2657 This used to be the only way to compare columns. Use the superior L</-ident>
2658 method for all new code. For example an identifier declared in such a way
2659 will be properly quoted if L</quote_char> is properly set, while the legacy
2660 form will remain as supplied.
2664 my %where = ( is_ready => \"", completed => { '>', '2012-12-21' } )
2666 $stmt = "WHERE completed > ? AND is_ready"
2667 @bind = ('2012-12-21')
2669 Using an empty string literal used to be the only way to express a boolean.
2670 For all new code please use the much more readable
2671 L<-bool|/Unary operators: bool> operator.
2677 These pages could go on for a while, since the nesting of the data
2678 structures this module can handle are pretty much unlimited (the
2679 module implements the C<WHERE> expansion as a recursive function
2680 internally). Your best bet is to "play around" with the module a
2681 little to see how the data structures behave, and choose the best
2682 format for your data based on that.
2684 And of course, all the values above will probably be replaced with
2685 variables gotten from forms or the command line. After all, if you
2686 knew everything ahead of time, you wouldn't have to worry about
2687 dynamically-generating SQL and could just hardwire it into your
2690 =head1 ORDER BY CLAUSES
2692 Some functions take an order by clause. This can either be a scalar (just a
2693 column name), a hashref of C<< { -desc => 'col' } >> or C<< { -asc => 'col' }
2694 >>, a scalarref, an arrayref-ref, or an arrayref of any of the previous
2697 Given | Will Generate
2698 ---------------------------------------------------------------
2700 'colA' | ORDER BY colA
2702 [qw/colA colB/] | ORDER BY colA, colB
2704 {-asc => 'colA'} | ORDER BY colA ASC
2706 {-desc => 'colB'} | ORDER BY colB DESC
2708 ['colA', {-asc => 'colB'}] | ORDER BY colA, colB ASC
2710 { -asc => [qw/colA colB/] } | ORDER BY colA ASC, colB ASC
2712 \'colA DESC' | ORDER BY colA DESC
2714 \[ 'FUNC(colA, ?)', $x ] | ORDER BY FUNC(colA, ?)
2715 | /* ...with $x bound to ? */
2718 { -asc => 'colA' }, | colA ASC,
2719 { -desc => [qw/colB/] }, | colB DESC,
2720 { -asc => [qw/colC colD/] },| colC ASC, colD ASC,
2721 \'colE DESC', | colE DESC,
2722 \[ 'FUNC(colF, ?)', $x ], | FUNC(colF, ?)
2723 ] | /* ...with $x bound to ? */
2724 ===============================================================
2728 =head1 SPECIAL OPERATORS
2730 my $sqlmaker = SQL::Abstract->new(special_ops => [
2734 my ($self, $field, $op, $arg) = @_;
2740 handler => 'method_name',
2744 A "special operator" is a SQL syntactic clause that can be
2745 applied to a field, instead of a usual binary operator.
2748 WHERE field IN (?, ?, ?)
2749 WHERE field BETWEEN ? AND ?
2750 WHERE MATCH(field) AGAINST (?, ?)
2752 Special operators IN and BETWEEN are fairly standard and therefore
2753 are builtin within C<SQL::Abstract> (as the overridable methods
2754 C<_where_field_IN> and C<_where_field_BETWEEN>). For other operators,
2755 like the MATCH .. AGAINST example above which is specific to MySQL,
2756 you can write your own operator handlers - supply a C<special_ops>
2757 argument to the C<new> method. That argument takes an arrayref of
2758 operator definitions; each operator definition is a hashref with two
2765 the regular expression to match the operator
2769 Either a coderef or a plain scalar method name. In both cases
2770 the expected return is C<< ($sql, @bind) >>.
2772 When supplied with a method name, it is simply called on the
2773 L<SQL::Abstract> object as:
2775 $self->$method_name($field, $op, $arg)
2779 $field is the LHS of the operator
2780 $op is the part that matched the handler regex
2783 When supplied with a coderef, it is called as:
2785 $coderef->($self, $field, $op, $arg)
2790 For example, here is an implementation
2791 of the MATCH .. AGAINST syntax for MySQL
2793 my $sqlmaker = SQL::Abstract->new(special_ops => [
2795 # special op for MySql MATCH (field) AGAINST(word1, word2, ...)
2796 {regex => qr/^match$/i,
2798 my ($self, $field, $op, $arg) = @_;
2799 $arg = [$arg] if not ref $arg;
2800 my $label = $self->_quote($field);
2801 my ($placeholder) = $self->_convert('?');
2802 my $placeholders = join ", ", (($placeholder) x @$arg);
2803 my $sql = $self->_sqlcase('match') . " ($label) "
2804 . $self->_sqlcase('against') . " ($placeholders) ";
2805 my @bind = $self->_bindtype($field, @$arg);
2806 return ($sql, @bind);
2813 =head1 UNARY OPERATORS
2815 my $sqlmaker = SQL::Abstract->new(unary_ops => [
2819 my ($self, $op, $arg) = @_;
2825 handler => 'method_name',
2829 A "unary operator" is a SQL syntactic clause that can be
2830 applied to a field - the operator goes before the field
2832 You can write your own operator handlers - supply a C<unary_ops>
2833 argument to the C<new> method. That argument takes an arrayref of
2834 operator definitions; each operator definition is a hashref with two
2841 the regular expression to match the operator
2845 Either a coderef or a plain scalar method name. In both cases
2846 the expected return is C<< $sql >>.
2848 When supplied with a method name, it is simply called on the
2849 L<SQL::Abstract> object as:
2851 $self->$method_name($op, $arg)
2855 $op is the part that matched the handler regex
2856 $arg is the RHS or argument of the operator
2858 When supplied with a coderef, it is called as:
2860 $coderef->($self, $op, $arg)
2868 Thanks to some benchmarking by Mark Stosberg, it turns out that
2869 this module is many orders of magnitude faster than using C<DBIx::Abstract>.
2870 I must admit this wasn't an intentional design issue, but it's a
2871 byproduct of the fact that you get to control your C<DBI> handles
2874 To maximize performance, use a code snippet like the following:
2876 # prepare a statement handle using the first row
2877 # and then reuse it for the rest of the rows
2879 for my $href (@array_of_hashrefs) {
2880 $stmt ||= $sql->insert('table', $href);
2881 $sth ||= $dbh->prepare($stmt);
2882 $sth->execute($sql->values($href));
2885 The reason this works is because the keys in your C<$href> are sorted
2886 internally by B<SQL::Abstract>. Thus, as long as your data retains
2887 the same structure, you only have to generate the SQL the first time
2888 around. On subsequent queries, simply use the C<values> function provided
2889 by this module to return your values in the correct order.
2891 However this depends on the values having the same type - if, for
2892 example, the values of a where clause may either have values
2893 (resulting in sql of the form C<column = ?> with a single bind
2894 value), or alternatively the values might be C<undef> (resulting in
2895 sql of the form C<column IS NULL> with no bind value) then the
2896 caching technique suggested will not work.
2900 If you use my C<CGI::FormBuilder> module at all, you'll hopefully
2901 really like this part (I do, at least). Building up a complex query
2902 can be as simple as the following:
2909 use CGI::FormBuilder;
2912 my $form = CGI::FormBuilder->new(...);
2913 my $sql = SQL::Abstract->new;
2915 if ($form->submitted) {
2916 my $field = $form->field;
2917 my $id = delete $field->{id};
2918 my($stmt, @bind) = $sql->update('table', $field, {id => $id});
2921 Of course, you would still have to connect using C<DBI> to run the
2922 query, but the point is that if you make your form look like your
2923 table, the actual query script can be extremely simplistic.
2925 If you're B<REALLY> lazy (I am), check out C<HTML::QuickTable> for
2926 a fast interface to returning and formatting data. I frequently
2927 use these three modules together to write complex database query
2928 apps in under 50 lines.
2930 =head1 HOW TO CONTRIBUTE
2932 Contributions are always welcome, in all usable forms (we especially
2933 welcome documentation improvements). The delivery methods include git-
2934 or unified-diff formatted patches, GitHub pull requests, or plain bug
2935 reports either via RT or the Mailing list. Contributors are generally
2936 granted full access to the official repository after their first several
2937 patches pass successful review.
2939 This project is maintained in a git repository. The code and related tools are
2940 accessible at the following locations:
2944 =item * Official repo: L<git://git.shadowcat.co.uk/dbsrgits/SQL-Abstract.git>
2946 =item * Official gitweb: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits/SQL-Abstract.git>
2948 =item * GitHub mirror: L<https://github.com/dbsrgits/sql-abstract>
2950 =item * Authorized committers: L<ssh://dbsrgits@git.shadowcat.co.uk/SQL-Abstract.git>
2956 Version 1.50 was a major internal refactoring of C<SQL::Abstract>.
2957 Great care has been taken to preserve the I<published> behavior
2958 documented in previous versions in the 1.* family; however,
2959 some features that were previously undocumented, or behaved
2960 differently from the documentation, had to be changed in order
2961 to clarify the semantics. Hence, client code that was relying
2962 on some dark areas of C<SQL::Abstract> v1.*
2963 B<might behave differently> in v1.50.
2965 The main changes are:
2971 support for literal SQL through the C<< \ [ $sql, @bind ] >> syntax.
2975 support for the { operator => \"..." } construct (to embed literal SQL)
2979 support for the { operator => \["...", @bind] } construct (to embed literal SQL with bind values)
2983 optional support for L<array datatypes|/"Inserting and Updating Arrays">
2987 defensive programming: check arguments
2991 fixed bug with global logic, which was previously implemented
2992 through global variables yielding side-effects. Prior versions would
2993 interpret C<< [ {cond1, cond2}, [cond3, cond4] ] >>
2994 as C<< "(cond1 AND cond2) OR (cond3 AND cond4)" >>.
2995 Now this is interpreted
2996 as C<< "(cond1 AND cond2) OR (cond3 OR cond4)" >>.
3001 fixed semantics of _bindtype on array args
3005 dropped the C<_anoncopy> of the %where tree. No longer necessary,
3006 we just avoid shifting arrays within that tree.
3010 dropped the C<_modlogic> function
3014 =head1 ACKNOWLEDGEMENTS
3016 There are a number of individuals that have really helped out with
3017 this module. Unfortunately, most of them submitted bugs via CPAN
3018 so I have no idea who they are! But the people I do know are:
3020 Ash Berlin (order_by hash term support)
3021 Matt Trout (DBIx::Class support)
3022 Mark Stosberg (benchmarking)
3023 Chas Owens (initial "IN" operator support)
3024 Philip Collins (per-field SQL functions)
3025 Eric Kolve (hashref "AND" support)
3026 Mike Fragassi (enhancements to "BETWEEN" and "LIKE")
3027 Dan Kubb (support for "quote_char" and "name_sep")
3028 Guillermo Roditi (patch to cleanup "IN" and "BETWEEN", fix and tests for _order_by)
3029 Laurent Dami (internal refactoring, extensible list of special operators, literal SQL)
3030 Norbert Buchmuller (support for literal SQL in hashpair, misc. fixes & tests)
3031 Peter Rabbitson (rewrite of SQLA::Test, misc. fixes & tests)
3032 Oliver Charles (support for "RETURNING" after "INSERT")
3038 L<DBIx::Class>, L<DBIx::Abstract>, L<CGI::FormBuilder>, L<HTML::QuickTable>.
3042 Copyright (c) 2001-2007 Nathan Wiger <nwiger@cpan.org>. All Rights Reserved.
3044 This module is actively maintained by Matt Trout <mst@shadowcatsystems.co.uk>
3046 For support, your best bet is to try the C<DBIx::Class> users mailing list.
3047 While not an official support venue, C<DBIx::Class> makes heavy use of
3048 C<SQL::Abstract>, and as such list members there are very familiar with
3049 how to create queries.
3053 This module is free software; you may copy this under the same
3054 terms as perl itself (either the GNU General Public License or
3055 the Artistic License)