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 +("-$_" => '_render_'.$_),
869 qw(op func value bind ident literal);
870 if (my $meth = $op{$k}) {
871 return $self->$meth($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";
904 my ($self, $ident) = @_;
906 return $self->_convert($self->_quote($ident));
910 my ($self, $value) = @_;
912 return ($self->_convert('?'), $self->_bindtype(undef, $value));
915 my %unop_postfix = map +($_ => 1),
916 'is null', 'is not null',
924 my ($self, $args) = @_;
925 my ($left, $low, $high) = @$args;
926 my ($rhsql, @rhbind) = do {
928 puke "Single arg to between must be a literal"
929 unless $low->{-literal};
932 my ($l, $h) = map [ $self->_render_expr($_) ], $low, $high;
933 (join(' ', $l->[0], $self->_sqlcase('and'), $h->[0]),
934 @{$l}[1..$#$l], @{$h}[1..$#$h])
937 my ($lhsql, @lhbind) = $self->_render_expr($left);
939 join(' ', '(', $lhsql, $self->_sqlcase($op), $rhsql, ')'),
943 }), 'between', 'not between'),
947 my ($self, $args) = @_;
948 my ($lhs, $rhs) = @$args;
951 my ($sql, @bind) = $self->_render_expr($_);
952 push @in_bind, @bind;
955 my ($lhsql, @lbind) = $self->_render_expr($lhs);
957 $lhsql.' '.$self->_sqlcase($op).' ( '
968 my ($op, @args) = @$v;
969 $op =~ s/^-// if length($op) > 1;
971 local $self->{_nested_func_lhs};
972 if (my $h = $special{$op}) {
973 return $self->$h(\@args);
975 if (my $us = List::Util::first { $op =~ $_->{regex} } @{$self->{user_special_ops}}) {
976 puke "Special op '${op}' requires first value to be identifier"
977 unless my ($k) = map $_->{-ident}, grep ref($_) eq 'HASH', $args[0];
978 return $self->${\($us->{handler})}($k, $op, $args[1]);
980 my $final_op = $op =~ /^(?:is|not)_/ ? join(' ', split '_', $op) : $op;
981 if (@args == 1 and $op !~ /^(and|or)$/) {
982 my ($expr_sql, @bind) = $self->_render_expr($args[0]);
983 my $op_sql = $self->_sqlcase($final_op);
985 $unop_postfix{lc($final_op)}
986 ? "${expr_sql} ${op_sql}"
987 : "${op_sql} ${expr_sql}"
989 return (($op eq 'not' ? '('.$final_sql.')' : $final_sql), @bind);
991 my @parts = map [ $self->_render_expr($_) ], @args;
992 my ($final_sql) = map +($op =~ /^(and|or)$/ ? "(${_})" : $_), join(
993 ' '.$self->_sqlcase($final_op).' ',
998 map @{$_}[1..$#$_], @parts
1005 my ($self, $rest) = @_;
1006 my ($func, @args) = @$rest;
1010 push @arg_sql, shift @x;
1012 } map [ $self->_render_expr($_) ], @args;
1013 return ($self->_sqlcase($func).'('.join(', ', @arg_sql).')', @bind);
1017 my ($self, $bind) = @_;
1018 return ($self->_convert('?'), $self->_bindtype(@$bind));
1021 sub _render_literal {
1022 my ($self, $literal) = @_;
1023 $self->_assert_bindval_matches_bindtype(@{$literal}[1..$#$literal]);
1027 # Some databases (SQLite) treat col IN (1, 2) different from
1028 # col IN ( (1, 2) ). Use this to strip all outer parens while
1029 # adding them back in the corresponding method
1030 sub _open_outer_paren {
1031 my ($self, $sql) = @_;
1033 while (my ($inner) = $sql =~ /^ \s* \( (.*) \) \s* $/xs) {
1035 # there are closing parens inside, need the heavy duty machinery
1036 # to reevaluate the extraction starting from $sql (full reevaluation)
1037 if ($inner =~ /\)/) {
1038 require Text::Balanced;
1040 my (undef, $remainder) = do {
1041 # idiotic design - writes to $@ but *DOES NOT* throw exceptions
1043 Text::Balanced::extract_bracketed($sql, '()', qr/\s*/);
1046 # the entire expression needs to be a balanced bracketed thing
1047 # (after an extract no remainder sans trailing space)
1048 last if defined $remainder and $remainder =~ /\S/;
1058 #======================================================================
1060 #======================================================================
1063 my ($self, $arg) = @_;
1065 return '' unless defined($arg);
1067 my @chunks = $self->_order_by_chunks($arg);
1071 my ($s, @b) = $self->_render_expr($_);
1078 $self->_sqlcase(' order by'),
1084 return wantarray ? ($sql, @bind) : $sql;
1087 sub _order_by_chunks {
1088 my ($self, $arg) = @_;
1090 if (ref($arg) eq 'ARRAY') {
1091 return map $self->_order_by_chunks($_), @$arg;
1093 if (my $l = is_literal_value($arg)) {
1094 return +{ -literal => $l };
1097 return +{ -ident => $arg };
1099 if (ref($arg) eq 'HASH') {
1100 my ($key, $val, @rest) = %$arg;
1102 return () unless $key;
1104 if (@rest or not $key =~ /^-(desc|asc)/i) {
1105 puke "hash passed to _order_by must have exactly one key (-desc or -asc)";
1110 map +{ -op => [ $dir, $_ ] }, $self->_order_by_chunks($val);
1115 #======================================================================
1116 # DATASOURCE (FOR NOW, JUST PLAIN TABLE OR LIST OF TABLES)
1117 #======================================================================
1122 $self->_SWITCH_refkind($from, {
1123 ARRAYREF => sub {join ', ', map { $self->_quote($_) } @$from;},
1124 SCALAR => sub {$self->_quote($from)},
1125 SCALARREF => sub {$$from},
1130 #======================================================================
1132 #======================================================================
1134 # highly optimized, as it's called way too often
1136 # my ($self, $label) = @_;
1138 return '' unless defined $_[1];
1139 return ${$_[1]} if ref($_[1]) eq 'SCALAR';
1141 $_[0]->{quote_char} or
1142 ($_[0]->_assert_pass_injection_guard($_[1]), return $_[1]);
1144 my $qref = ref $_[0]->{quote_char};
1146 !$qref ? ($_[0]->{quote_char}, $_[0]->{quote_char})
1147 : ($qref eq 'ARRAY') ? @{$_[0]->{quote_char}}
1148 : puke "Unsupported quote_char format: $_[0]->{quote_char}";
1150 my $esc = $_[0]->{escape_char} || $r;
1152 # parts containing * are naturally unquoted
1153 return join($_[0]->{name_sep}||'', map
1154 +( $_ eq '*' ? $_ : do { (my $n = $_) =~ s/(\Q$esc\E|\Q$r\E)/$esc$1/g; $l . $n . $r } ),
1155 ( $_[0]->{name_sep} ? split (/\Q$_[0]->{name_sep}\E/, $_[1] ) : $_[1] )
1160 # Conversion, if applicable
1162 #my ($self, $arg) = @_;
1163 if ($_[0]->{convert}) {
1164 return $_[0]->_sqlcase($_[0]->{convert}) .'(' . $_[1] . ')';
1171 #my ($self, $col, @vals) = @_;
1172 # called often - tighten code
1173 return $_[0]->{bindtype} eq 'columns'
1174 ? map {[$_[1], $_]} @_[2 .. $#_]
1179 # Dies if any element of @bind is not in [colname => value] format
1180 # if bindtype is 'columns'.
1181 sub _assert_bindval_matches_bindtype {
1182 # my ($self, @bind) = @_;
1184 if ($self->{bindtype} eq 'columns') {
1186 if (!defined $_ || ref($_) ne 'ARRAY' || @$_ != 2) {
1187 puke "bindtype 'columns' selected, you need to pass: [column_name => bind_value]"
1193 sub _join_sql_clauses {
1194 my ($self, $logic, $clauses_aref, $bind_aref) = @_;
1196 if (@$clauses_aref > 1) {
1197 my $join = " " . $self->_sqlcase($logic) . " ";
1198 my $sql = '( ' . join($join, @$clauses_aref) . ' )';
1199 return ($sql, @$bind_aref);
1201 elsif (@$clauses_aref) {
1202 return ($clauses_aref->[0], @$bind_aref); # no parentheses
1205 return (); # if no SQL, ignore @$bind_aref
1210 # Fix SQL case, if so requested
1212 # LDNOTE: if $self->{case} is true, then it contains 'lower', so we
1213 # don't touch the argument ... crooked logic, but let's not change it!
1214 return $_[0]->{case} ? $_[1] : uc($_[1]);
1218 #======================================================================
1219 # DISPATCHING FROM REFKIND
1220 #======================================================================
1223 my ($self, $data) = @_;
1225 return 'UNDEF' unless defined $data;
1227 # blessed objects are treated like scalars
1228 my $ref = (Scalar::Util::blessed $data) ? '' : ref $data;
1230 return 'SCALAR' unless $ref;
1233 while ($ref eq 'REF') {
1235 $ref = (Scalar::Util::blessed $data) ? '' : ref $data;
1239 return ($ref||'SCALAR') . ('REF' x $n_steps);
1243 my ($self, $data) = @_;
1244 my @try = ($self->_refkind($data));
1245 push @try, 'SCALAR_or_UNDEF' if $try[0] eq 'SCALAR' || $try[0] eq 'UNDEF';
1246 push @try, 'FALLBACK';
1250 sub _METHOD_FOR_refkind {
1251 my ($self, $meth_prefix, $data) = @_;
1254 for (@{$self->_try_refkind($data)}) {
1255 $method = $self->can($meth_prefix."_".$_)
1259 return $method || puke "cannot dispatch on '$meth_prefix' for ".$self->_refkind($data);
1263 sub _SWITCH_refkind {
1264 my ($self, $data, $dispatch_table) = @_;
1267 for (@{$self->_try_refkind($data)}) {
1268 $coderef = $dispatch_table->{$_}
1272 puke "no dispatch entry for ".$self->_refkind($data)
1281 #======================================================================
1282 # VALUES, GENERATE, AUTOLOAD
1283 #======================================================================
1285 # LDNOTE: original code from nwiger, didn't touch code in that section
1286 # I feel the AUTOLOAD stuff should not be the default, it should
1287 # only be activated on explicit demand by user.
1291 my $data = shift || return;
1292 puke "Argument to ", __PACKAGE__, "->values must be a \\%hash"
1293 unless ref $data eq 'HASH';
1296 foreach my $k (sort keys %$data) {
1297 my $v = $data->{$k};
1298 $self->_SWITCH_refkind($v, {
1300 if ($self->{array_datatypes}) { # array datatype
1301 push @all_bind, $self->_bindtype($k, $v);
1303 else { # literal SQL with bind
1304 my ($sql, @bind) = @$v;
1305 $self->_assert_bindval_matches_bindtype(@bind);
1306 push @all_bind, @bind;
1309 ARRAYREFREF => sub { # literal SQL with bind
1310 my ($sql, @bind) = @${$v};
1311 $self->_assert_bindval_matches_bindtype(@bind);
1312 push @all_bind, @bind;
1314 SCALARREF => sub { # literal SQL without bind
1316 SCALAR_or_UNDEF => sub {
1317 push @all_bind, $self->_bindtype($k, $v);
1328 my(@sql, @sqlq, @sqlv);
1332 if ($ref eq 'HASH') {
1333 for my $k (sort keys %$_) {
1336 my $label = $self->_quote($k);
1337 if ($r eq 'ARRAY') {
1338 # literal SQL with bind
1339 my ($sql, @bind) = @$v;
1340 $self->_assert_bindval_matches_bindtype(@bind);
1341 push @sqlq, "$label = $sql";
1343 } elsif ($r eq 'SCALAR') {
1344 # literal SQL without bind
1345 push @sqlq, "$label = $$v";
1347 push @sqlq, "$label = ?";
1348 push @sqlv, $self->_bindtype($k, $v);
1351 push @sql, $self->_sqlcase('set'), join ', ', @sqlq;
1352 } elsif ($ref eq 'ARRAY') {
1353 # unlike insert(), assume these are ONLY the column names, i.e. for SQL
1356 if ($r eq 'ARRAY') { # literal SQL with bind
1357 my ($sql, @bind) = @$v;
1358 $self->_assert_bindval_matches_bindtype(@bind);
1361 } elsif ($r eq 'SCALAR') { # literal SQL without bind
1362 # embedded literal SQL
1369 push @sql, '(' . join(', ', @sqlq) . ')';
1370 } elsif ($ref eq 'SCALAR') {
1374 # strings get case twiddled
1375 push @sql, $self->_sqlcase($_);
1379 my $sql = join ' ', @sql;
1381 # this is pretty tricky
1382 # if ask for an array, return ($stmt, @bind)
1383 # otherwise, s/?/shift @sqlv/ to put it inline
1385 return ($sql, @sqlv);
1387 1 while $sql =~ s/\?/my $d = shift(@sqlv);
1388 ref $d ? $d->[1] : $d/e;
1397 # This allows us to check for a local, then _form, attr
1399 my($name) = $AUTOLOAD =~ /.*::(.+)/;
1400 return $self->generate($name, @_);
1411 SQL::Abstract - Generate SQL from Perl data structures
1417 my $sql = SQL::Abstract->new;
1419 my($stmt, @bind) = $sql->select($source, \@fields, \%where, $order);
1421 my($stmt, @bind) = $sql->insert($table, \%fieldvals || \@values);
1423 my($stmt, @bind) = $sql->update($table, \%fieldvals, \%where);
1425 my($stmt, @bind) = $sql->delete($table, \%where);
1427 # Then, use these in your DBI statements
1428 my $sth = $dbh->prepare($stmt);
1429 $sth->execute(@bind);
1431 # Just generate the WHERE clause
1432 my($stmt, @bind) = $sql->where(\%where, $order);
1434 # Return values in the same order, for hashed queries
1435 # See PERFORMANCE section for more details
1436 my @bind = $sql->values(\%fieldvals);
1440 This module was inspired by the excellent L<DBIx::Abstract>.
1441 However, in using that module I found that what I really wanted
1442 to do was generate SQL, but still retain complete control over my
1443 statement handles and use the DBI interface. So, I set out to
1444 create an abstract SQL generation module.
1446 While based on the concepts used by L<DBIx::Abstract>, there are
1447 several important differences, especially when it comes to WHERE
1448 clauses. I have modified the concepts used to make the SQL easier
1449 to generate from Perl data structures and, IMO, more intuitive.
1450 The underlying idea is for this module to do what you mean, based
1451 on the data structures you provide it. The big advantage is that
1452 you don't have to modify your code every time your data changes,
1453 as this module figures it out.
1455 To begin with, an SQL INSERT is as easy as just specifying a hash
1456 of C<key=value> pairs:
1459 name => 'Jimbo Bobson',
1460 phone => '123-456-7890',
1461 address => '42 Sister Lane',
1462 city => 'St. Louis',
1463 state => 'Louisiana',
1466 The SQL can then be generated with this:
1468 my($stmt, @bind) = $sql->insert('people', \%data);
1470 Which would give you something like this:
1472 $stmt = "INSERT INTO people
1473 (address, city, name, phone, state)
1474 VALUES (?, ?, ?, ?, ?)";
1475 @bind = ('42 Sister Lane', 'St. Louis', 'Jimbo Bobson',
1476 '123-456-7890', 'Louisiana');
1478 These are then used directly in your DBI code:
1480 my $sth = $dbh->prepare($stmt);
1481 $sth->execute(@bind);
1483 =head2 Inserting and Updating Arrays
1485 If your database has array types (like for example Postgres),
1486 activate the special option C<< array_datatypes => 1 >>
1487 when creating the C<SQL::Abstract> object.
1488 Then you may use an arrayref to insert and update database array types:
1490 my $sql = SQL::Abstract->new(array_datatypes => 1);
1492 planets => [qw/Mercury Venus Earth Mars/]
1495 my($stmt, @bind) = $sql->insert('solar_system', \%data);
1499 $stmt = "INSERT INTO solar_system (planets) VALUES (?)"
1501 @bind = (['Mercury', 'Venus', 'Earth', 'Mars']);
1504 =head2 Inserting and Updating SQL
1506 In order to apply SQL functions to elements of your C<%data> you may
1507 specify a reference to an arrayref for the given hash value. For example,
1508 if you need to execute the Oracle C<to_date> function on a value, you can
1509 say something like this:
1513 date_entered => \[ "to_date(?,'MM/DD/YYYY')", "03/02/2003" ],
1516 The first value in the array is the actual SQL. Any other values are
1517 optional and would be included in the bind values array. This gives
1520 my($stmt, @bind) = $sql->insert('people', \%data);
1522 $stmt = "INSERT INTO people (name, date_entered)
1523 VALUES (?, to_date(?,'MM/DD/YYYY'))";
1524 @bind = ('Bill', '03/02/2003');
1526 An UPDATE is just as easy, all you change is the name of the function:
1528 my($stmt, @bind) = $sql->update('people', \%data);
1530 Notice that your C<%data> isn't touched; the module will generate
1531 the appropriately quirky SQL for you automatically. Usually you'll
1532 want to specify a WHERE clause for your UPDATE, though, which is
1533 where handling C<%where> hashes comes in handy...
1535 =head2 Complex where statements
1537 This module can generate pretty complicated WHERE statements
1538 easily. For example, simple C<key=value> pairs are taken to mean
1539 equality, and if you want to see if a field is within a set
1540 of values, you can use an arrayref. Let's say we wanted to
1541 SELECT some data based on this criteria:
1544 requestor => 'inna',
1545 worker => ['nwiger', 'rcwe', 'sfz'],
1546 status => { '!=', 'completed' }
1549 my($stmt, @bind) = $sql->select('tickets', '*', \%where);
1551 The above would give you something like this:
1553 $stmt = "SELECT * FROM tickets WHERE
1554 ( requestor = ? ) AND ( status != ? )
1555 AND ( worker = ? OR worker = ? OR worker = ? )";
1556 @bind = ('inna', 'completed', 'nwiger', 'rcwe', 'sfz');
1558 Which you could then use in DBI code like so:
1560 my $sth = $dbh->prepare($stmt);
1561 $sth->execute(@bind);
1567 The methods are simple. There's one for every major SQL operation,
1568 and a constructor you use first. The arguments are specified in a
1569 similar order for each method (table, then fields, then a where
1570 clause) to try and simplify things.
1572 =head2 new(option => 'value')
1574 The C<new()> function takes a list of options and values, and returns
1575 a new B<SQL::Abstract> object which can then be used to generate SQL
1576 through the methods below. The options accepted are:
1582 If set to 'lower', then SQL will be generated in all lowercase. By
1583 default SQL is generated in "textbook" case meaning something like:
1585 SELECT a_field FROM a_table WHERE some_field LIKE '%someval%'
1587 Any setting other than 'lower' is ignored.
1591 This determines what the default comparison operator is. By default
1592 it is C<=>, meaning that a hash like this:
1594 %where = (name => 'nwiger', email => 'nate@wiger.org');
1596 Will generate SQL like this:
1598 WHERE name = 'nwiger' AND email = 'nate@wiger.org'
1600 However, you may want loose comparisons by default, so if you set
1601 C<cmp> to C<like> you would get SQL such as:
1603 WHERE name like 'nwiger' AND email like 'nate@wiger.org'
1605 You can also override the comparison on an individual basis - see
1606 the huge section on L</"WHERE CLAUSES"> at the bottom.
1608 =item sqltrue, sqlfalse
1610 Expressions for inserting boolean values within SQL statements.
1611 By default these are C<1=1> and C<1=0>. They are used
1612 by the special operators C<-in> and C<-not_in> for generating
1613 correct SQL even when the argument is an empty array (see below).
1617 This determines the default logical operator for multiple WHERE
1618 statements in arrays or hashes. If absent, the default logic is "or"
1619 for arrays, and "and" for hashes. This means that a WHERE
1623 event_date => {'>=', '2/13/99'},
1624 event_date => {'<=', '4/24/03'},
1627 will generate SQL like this:
1629 WHERE event_date >= '2/13/99' OR event_date <= '4/24/03'
1631 This is probably not what you want given this query, though (look
1632 at the dates). To change the "OR" to an "AND", simply specify:
1634 my $sql = SQL::Abstract->new(logic => 'and');
1636 Which will change the above C<WHERE> to:
1638 WHERE event_date >= '2/13/99' AND event_date <= '4/24/03'
1640 The logic can also be changed locally by inserting
1641 a modifier in front of an arrayref:
1643 @where = (-and => [event_date => {'>=', '2/13/99'},
1644 event_date => {'<=', '4/24/03'} ]);
1646 See the L</"WHERE CLAUSES"> section for explanations.
1650 This will automatically convert comparisons using the specified SQL
1651 function for both column and value. This is mostly used with an argument
1652 of C<upper> or C<lower>, so that the SQL will have the effect of
1653 case-insensitive "searches". For example, this:
1655 $sql = SQL::Abstract->new(convert => 'upper');
1656 %where = (keywords => 'MaKe iT CAse inSeNSItive');
1658 Will turn out the following SQL:
1660 WHERE upper(keywords) like upper('MaKe iT CAse inSeNSItive')
1662 The conversion can be C<upper()>, C<lower()>, or any other SQL function
1663 that can be applied symmetrically to fields (actually B<SQL::Abstract> does
1664 not validate this option; it will just pass through what you specify verbatim).
1668 This is a kludge because many databases suck. For example, you can't
1669 just bind values using DBI's C<execute()> for Oracle C<CLOB> or C<BLOB> fields.
1670 Instead, you have to use C<bind_param()>:
1672 $sth->bind_param(1, 'reg data');
1673 $sth->bind_param(2, $lots, {ora_type => ORA_CLOB});
1675 The problem is, B<SQL::Abstract> will normally just return a C<@bind> array,
1676 which loses track of which field each slot refers to. Fear not.
1678 If you specify C<bindtype> in new, you can determine how C<@bind> is returned.
1679 Currently, you can specify either C<normal> (default) or C<columns>. If you
1680 specify C<columns>, you will get an array that looks like this:
1682 my $sql = SQL::Abstract->new(bindtype => 'columns');
1683 my($stmt, @bind) = $sql->insert(...);
1686 [ 'column1', 'value1' ],
1687 [ 'column2', 'value2' ],
1688 [ 'column3', 'value3' ],
1691 You can then iterate through this manually, using DBI's C<bind_param()>.
1693 $sth->prepare($stmt);
1696 my($col, $data) = @$_;
1697 if ($col eq 'details' || $col eq 'comments') {
1698 $sth->bind_param($i, $data, {ora_type => ORA_CLOB});
1699 } elsif ($col eq 'image') {
1700 $sth->bind_param($i, $data, {ora_type => ORA_BLOB});
1702 $sth->bind_param($i, $data);
1706 $sth->execute; # execute without @bind now
1708 Now, why would you still use B<SQL::Abstract> if you have to do this crap?
1709 Basically, the advantage is still that you don't have to care which fields
1710 are or are not included. You could wrap that above C<for> loop in a simple
1711 sub called C<bind_fields()> or something and reuse it repeatedly. You still
1712 get a layer of abstraction over manual SQL specification.
1714 Note that if you set L</bindtype> to C<columns>, the C<\[ $sql, @bind ]>
1715 construct (see L</Literal SQL with placeholders and bind values (subqueries)>)
1716 will expect the bind values in this format.
1720 This is the character that a table or column name will be quoted
1721 with. By default this is an empty string, but you could set it to
1722 the character C<`>, to generate SQL like this:
1724 SELECT `a_field` FROM `a_table` WHERE `some_field` LIKE '%someval%'
1726 Alternatively, you can supply an array ref of two items, the first being the left
1727 hand quote character, and the second the right hand quote character. For
1728 example, you could supply C<['[',']']> for SQL Server 2000 compliant quotes
1729 that generates SQL like this:
1731 SELECT [a_field] FROM [a_table] WHERE [some_field] LIKE '%someval%'
1733 Quoting is useful if you have tables or columns names that are reserved
1734 words in your database's SQL dialect.
1738 This is the character that will be used to escape L</quote_char>s appearing
1739 in an identifier before it has been quoted.
1741 The parameter default in case of a single L</quote_char> character is the quote
1744 When opening-closing-style quoting is used (L</quote_char> is an arrayref)
1745 this parameter defaults to the B<closing (right)> L</quote_char>. Occurrences
1746 of the B<opening (left)> L</quote_char> within the identifier are currently left
1747 untouched. The default for opening-closing-style quotes may change in future
1748 versions, thus you are B<strongly encouraged> to specify the escape character
1753 This is the character that separates a table and column name. It is
1754 necessary to specify this when the C<quote_char> option is selected,
1755 so that tables and column names can be individually quoted like this:
1757 SELECT `table`.`one_field` FROM `table` WHERE `table`.`other_field` = 1
1759 =item injection_guard
1761 A regular expression C<qr/.../> that is applied to any C<-function> and unquoted
1762 column name specified in a query structure. This is a safety mechanism to avoid
1763 injection attacks when mishandling user input e.g.:
1765 my %condition_as_column_value_pairs = get_values_from_user();
1766 $sqla->select( ... , \%condition_as_column_value_pairs );
1768 If the expression matches an exception is thrown. Note that literal SQL
1769 supplied via C<\'...'> or C<\['...']> is B<not> checked in any way.
1771 Defaults to checking for C<;> and the C<GO> keyword (TransactSQL)
1773 =item array_datatypes
1775 When this option is true, arrayrefs in INSERT or UPDATE are
1776 interpreted as array datatypes and are passed directly
1778 When this option is false, arrayrefs are interpreted
1779 as literal SQL, just like refs to arrayrefs
1780 (but this behavior is for backwards compatibility; when writing
1781 new queries, use the "reference to arrayref" syntax
1787 Takes a reference to a list of "special operators"
1788 to extend the syntax understood by L<SQL::Abstract>.
1789 See section L</"SPECIAL OPERATORS"> for details.
1793 Takes a reference to a list of "unary operators"
1794 to extend the syntax understood by L<SQL::Abstract>.
1795 See section L</"UNARY OPERATORS"> for details.
1801 =head2 insert($table, \@values || \%fieldvals, \%options)
1803 This is the simplest function. You simply give it a table name
1804 and either an arrayref of values or hashref of field/value pairs.
1805 It returns an SQL INSERT statement and a list of bind values.
1806 See the sections on L</"Inserting and Updating Arrays"> and
1807 L</"Inserting and Updating SQL"> for information on how to insert
1808 with those data types.
1810 The optional C<\%options> hash reference may contain additional
1811 options to generate the insert SQL. Currently supported options
1818 Takes either a scalar of raw SQL fields, or an array reference of
1819 field names, and adds on an SQL C<RETURNING> statement at the end.
1820 This allows you to return data generated by the insert statement
1821 (such as row IDs) without performing another C<SELECT> statement.
1822 Note, however, this is not part of the SQL standard and may not
1823 be supported by all database engines.
1827 =head2 update($table, \%fieldvals, \%where, \%options)
1829 This takes a table, hashref of field/value pairs, and an optional
1830 hashref L<WHERE clause|/WHERE CLAUSES>. It returns an SQL UPDATE function and a list
1832 See the sections on L</"Inserting and Updating Arrays"> and
1833 L</"Inserting and Updating SQL"> for information on how to insert
1834 with those data types.
1836 The optional C<\%options> hash reference may contain additional
1837 options to generate the update SQL. Currently supported options
1844 See the C<returning> option to
1845 L<insert|/insert($table, \@values || \%fieldvals, \%options)>.
1849 =head2 select($source, $fields, $where, $order)
1851 This returns a SQL SELECT statement and associated list of bind values, as
1852 specified by the arguments:
1858 Specification of the 'FROM' part of the statement.
1859 The argument can be either a plain scalar (interpreted as a table
1860 name, will be quoted), or an arrayref (interpreted as a list
1861 of table names, joined by commas, quoted), or a scalarref
1862 (literal SQL, not quoted).
1866 Specification of the list of fields to retrieve from
1868 The argument can be either an arrayref (interpreted as a list
1869 of field names, will be joined by commas and quoted), or a
1870 plain scalar (literal SQL, not quoted).
1871 Please observe that this API is not as flexible as that of
1872 the first argument C<$source>, for backwards compatibility reasons.
1876 Optional argument to specify the WHERE part of the query.
1877 The argument is most often a hashref, but can also be
1878 an arrayref or plain scalar --
1879 see section L<WHERE clause|/"WHERE CLAUSES"> for details.
1883 Optional argument to specify the ORDER BY part of the query.
1884 The argument can be a scalar, a hashref or an arrayref
1885 -- see section L<ORDER BY clause|/"ORDER BY CLAUSES">
1891 =head2 delete($table, \%where, \%options)
1893 This takes a table name and optional hashref L<WHERE clause|/WHERE CLAUSES>.
1894 It returns an SQL DELETE statement and list of bind values.
1896 The optional C<\%options> hash reference may contain additional
1897 options to generate the delete SQL. Currently supported options
1904 See the C<returning> option to
1905 L<insert|/insert($table, \@values || \%fieldvals, \%options)>.
1909 =head2 where(\%where, $order)
1911 This is used to generate just the WHERE clause. For example,
1912 if you have an arbitrary data structure and know what the
1913 rest of your SQL is going to look like, but want an easy way
1914 to produce a WHERE clause, use this. It returns an SQL WHERE
1915 clause and list of bind values.
1918 =head2 values(\%data)
1920 This just returns the values from the hash C<%data>, in the same
1921 order that would be returned from any of the other above queries.
1922 Using this allows you to markedly speed up your queries if you
1923 are affecting lots of rows. See below under the L</"PERFORMANCE"> section.
1925 =head2 generate($any, 'number', $of, \@data, $struct, \%types)
1927 Warning: This is an experimental method and subject to change.
1929 This returns arbitrarily generated SQL. It's a really basic shortcut.
1930 It will return two different things, depending on return context:
1932 my($stmt, @bind) = $sql->generate('create table', \$table, \@fields);
1933 my $stmt_and_val = $sql->generate('create table', \$table, \@fields);
1935 These would return the following:
1937 # First calling form
1938 $stmt = "CREATE TABLE test (?, ?)";
1939 @bind = (field1, field2);
1941 # Second calling form
1942 $stmt_and_val = "CREATE TABLE test (field1, field2)";
1944 Depending on what you're trying to do, it's up to you to choose the correct
1945 format. In this example, the second form is what you would want.
1949 $sql->generate('alter session', { nls_date_format => 'MM/YY' });
1953 ALTER SESSION SET nls_date_format = 'MM/YY'
1955 You get the idea. Strings get their case twiddled, but everything
1956 else remains verbatim.
1958 =head1 EXPORTABLE FUNCTIONS
1960 =head2 is_plain_value
1962 Determines if the supplied argument is a plain value as understood by this
1967 =item * The value is C<undef>
1969 =item * The value is a non-reference
1971 =item * The value is an object with stringification overloading
1973 =item * The value is of the form C<< { -value => $anything } >>
1977 On failure returns C<undef>, on success returns a B<scalar> reference
1978 to the original supplied argument.
1984 The stringification overloading detection is rather advanced: it takes
1985 into consideration not only the presence of a C<""> overload, but if that
1986 fails also checks for enabled
1987 L<autogenerated versions of C<"">|overload/Magic Autogeneration>, based
1988 on either C<0+> or C<bool>.
1990 Unfortunately testing in the field indicates that this
1991 detection B<< may tickle a latent bug in perl versions before 5.018 >>,
1992 but only when very large numbers of stringifying objects are involved.
1993 At the time of writing ( Sep 2014 ) there is no clear explanation of
1994 the direct cause, nor is there a manageably small test case that reliably
1995 reproduces the problem.
1997 If you encounter any of the following exceptions in B<random places within
1998 your application stack> - this module may be to blame:
2000 Operation "ne": no method found,
2001 left argument in overloaded package <something>,
2002 right argument in overloaded package <something>
2006 Stub found while resolving method "???" overloading """" in package <something>
2008 If you fall victim to the above - please attempt to reduce the problem
2009 to something that could be sent to the L<SQL::Abstract developers
2010 |DBIx::Class/GETTING HELP/SUPPORT>
2011 (either publicly or privately). As a workaround in the meantime you can
2012 set C<$ENV{SQLA_ISVALUE_IGNORE_AUTOGENERATED_STRINGIFICATION}> to a true
2013 value, which will most likely eliminate your problem (at the expense of
2014 not being able to properly detect exotic forms of stringification).
2016 This notice and environment variable will be removed in a future version,
2017 as soon as the underlying problem is found and a reliable workaround is
2022 =head2 is_literal_value
2024 Determines if the supplied argument is a literal value as understood by this
2029 =item * C<\$sql_string>
2031 =item * C<\[ $sql_string, @bind_values ]>
2035 On failure returns C<undef>, on success returns an B<array> reference
2036 containing the unpacked version of the supplied literal SQL and bind values.
2038 =head1 WHERE CLAUSES
2042 This module uses a variation on the idea from L<DBIx::Abstract>. It
2043 is B<NOT>, repeat I<not> 100% compatible. B<The main logic of this
2044 module is that things in arrays are OR'ed, and things in hashes
2047 The easiest way to explain is to show lots of examples. After
2048 each C<%where> hash shown, it is assumed you used:
2050 my($stmt, @bind) = $sql->where(\%where);
2052 However, note that the C<%where> hash can be used directly in any
2053 of the other functions as well, as described above.
2055 =head2 Key-value pairs
2057 So, let's get started. To begin, a simple hash:
2061 status => 'completed'
2064 Is converted to SQL C<key = val> statements:
2066 $stmt = "WHERE user = ? AND status = ?";
2067 @bind = ('nwiger', 'completed');
2069 One common thing I end up doing is having a list of values that
2070 a field can be in. To do this, simply specify a list inside of
2075 status => ['assigned', 'in-progress', 'pending'];
2078 This simple code will create the following:
2080 $stmt = "WHERE user = ? AND ( status = ? OR status = ? OR status = ? )";
2081 @bind = ('nwiger', 'assigned', 'in-progress', 'pending');
2083 A field associated to an empty arrayref will be considered a
2084 logical false and will generate 0=1.
2086 =head2 Tests for NULL values
2088 If the value part is C<undef> then this is converted to SQL <IS NULL>
2097 $stmt = "WHERE user = ? AND status IS NULL";
2100 To test if a column IS NOT NULL:
2104 status => { '!=', undef },
2107 =head2 Specific comparison operators
2109 If you want to specify a different type of operator for your comparison,
2110 you can use a hashref for a given column:
2114 status => { '!=', 'completed' }
2117 Which would generate:
2119 $stmt = "WHERE user = ? AND status != ?";
2120 @bind = ('nwiger', 'completed');
2122 To test against multiple values, just enclose the values in an arrayref:
2124 status => { '=', ['assigned', 'in-progress', 'pending'] };
2126 Which would give you:
2128 "WHERE status = ? OR status = ? OR status = ?"
2131 The hashref can also contain multiple pairs, in which case it is expanded
2132 into an C<AND> of its elements:
2136 status => { '!=', 'completed', -not_like => 'pending%' }
2139 # Or more dynamically, like from a form
2140 $where{user} = 'nwiger';
2141 $where{status}{'!='} = 'completed';
2142 $where{status}{'-not_like'} = 'pending%';
2144 # Both generate this
2145 $stmt = "WHERE user = ? AND status != ? AND status NOT LIKE ?";
2146 @bind = ('nwiger', 'completed', 'pending%');
2149 To get an OR instead, you can combine it with the arrayref idea:
2153 priority => [ { '=', 2 }, { '>', 5 } ]
2156 Which would generate:
2158 $stmt = "WHERE ( priority = ? OR priority > ? ) AND user = ?";
2159 @bind = ('2', '5', 'nwiger');
2161 If you want to include literal SQL (with or without bind values), just use a
2162 scalar reference or reference to an arrayref as the value:
2165 date_entered => { '>' => \["to_date(?, 'MM/DD/YYYY')", "11/26/2008"] },
2166 date_expires => { '<' => \"now()" }
2169 Which would generate:
2171 $stmt = "WHERE date_entered > to_date(?, 'MM/DD/YYYY') AND date_expires < now()";
2172 @bind = ('11/26/2008');
2175 =head2 Logic and nesting operators
2177 In the example above,
2178 there is a subtle trap if you want to say something like
2179 this (notice the C<AND>):
2181 WHERE priority != ? AND priority != ?
2183 Because, in Perl you I<can't> do this:
2185 priority => { '!=' => 2, '!=' => 1 }
2187 As the second C<!=> key will obliterate the first. The solution
2188 is to use the special C<-modifier> form inside an arrayref:
2190 priority => [ -and => {'!=', 2},
2194 Normally, these would be joined by C<OR>, but the modifier tells it
2195 to use C<AND> instead. (Hint: You can use this in conjunction with the
2196 C<logic> option to C<new()> in order to change the way your queries
2197 work by default.) B<Important:> Note that the C<-modifier> goes
2198 B<INSIDE> the arrayref, as an extra first element. This will
2199 B<NOT> do what you think it might:
2201 priority => -and => [{'!=', 2}, {'!=', 1}] # WRONG!
2203 Here is a quick list of equivalencies, since there is some overlap:
2206 status => {'!=', 'completed', 'not like', 'pending%' }
2207 status => [ -and => {'!=', 'completed'}, {'not like', 'pending%'}]
2210 status => {'=', ['assigned', 'in-progress']}
2211 status => [ -or => {'=', 'assigned'}, {'=', 'in-progress'}]
2212 status => [ {'=', 'assigned'}, {'=', 'in-progress'} ]
2216 =head2 Special operators: IN, BETWEEN, etc.
2218 You can also use the hashref format to compare a list of fields using the
2219 C<IN> comparison operator, by specifying the list as an arrayref:
2222 status => 'completed',
2223 reportid => { -in => [567, 2335, 2] }
2226 Which would generate:
2228 $stmt = "WHERE status = ? AND reportid IN (?,?,?)";
2229 @bind = ('completed', '567', '2335', '2');
2231 The reverse operator C<-not_in> generates SQL C<NOT IN> and is used in
2234 If the argument to C<-in> is an empty array, 'sqlfalse' is generated
2235 (by default: C<1=0>). Similarly, C<< -not_in => [] >> generates
2236 'sqltrue' (by default: C<1=1>).
2238 In addition to the array you can supply a chunk of literal sql or
2239 literal sql with bind:
2242 customer => { -in => \[
2243 'SELECT cust_id FROM cust WHERE balance > ?',
2246 status => { -in => \'SELECT status_codes FROM states' },
2252 customer IN ( SELECT cust_id FROM cust WHERE balance > ? )
2253 AND status IN ( SELECT status_codes FROM states )
2257 Finally, if the argument to C<-in> is not a reference, it will be
2258 treated as a single-element array.
2260 Another pair of operators is C<-between> and C<-not_between>,
2261 used with an arrayref of two values:
2265 completion_date => {
2266 -not_between => ['2002-10-01', '2003-02-06']
2272 WHERE user = ? AND completion_date NOT BETWEEN ( ? AND ? )
2274 Just like with C<-in> all plausible combinations of literal SQL
2278 start0 => { -between => [ 1, 2 ] },
2279 start1 => { -between => \["? AND ?", 1, 2] },
2280 start2 => { -between => \"lower(x) AND upper(y)" },
2281 start3 => { -between => [
2283 \["upper(?)", 'stuff' ],
2290 ( start0 BETWEEN ? AND ? )
2291 AND ( start1 BETWEEN ? AND ? )
2292 AND ( start2 BETWEEN lower(x) AND upper(y) )
2293 AND ( start3 BETWEEN lower(x) AND upper(?) )
2295 @bind = (1, 2, 1, 2, 'stuff');
2298 These are the two builtin "special operators"; but the
2299 list can be expanded: see section L</"SPECIAL OPERATORS"> below.
2301 =head2 Unary operators: bool
2303 If you wish to test against boolean columns or functions within your
2304 database you can use the C<-bool> and C<-not_bool> operators. For
2305 example to test the column C<is_user> being true and the column
2306 C<is_enabled> being false you would use:-
2310 -not_bool => 'is_enabled',
2315 WHERE is_user AND NOT is_enabled
2317 If a more complex combination is required, testing more conditions,
2318 then you should use the and/or operators:-
2323 -not_bool => { two=> { -rlike => 'bar' } },
2324 -not_bool => { three => [ { '=', 2 }, { '>', 5 } ] },
2335 (NOT ( three = ? OR three > ? ))
2338 =head2 Nested conditions, -and/-or prefixes
2340 So far, we've seen how multiple conditions are joined with a top-level
2341 C<AND>. We can change this by putting the different conditions we want in
2342 hashes and then putting those hashes in an array. For example:
2347 status => { -like => ['pending%', 'dispatched'] },
2351 status => 'unassigned',
2355 This data structure would create the following:
2357 $stmt = "WHERE ( user = ? AND ( status LIKE ? OR status LIKE ? ) )
2358 OR ( user = ? AND status = ? ) )";
2359 @bind = ('nwiger', 'pending', 'dispatched', 'robot', 'unassigned');
2362 Clauses in hashrefs or arrayrefs can be prefixed with an C<-and> or C<-or>
2363 to change the logic inside:
2369 -and => [ workhrs => {'>', 20}, geo => 'ASIA' ],
2370 -or => { workhrs => {'<', 50}, geo => 'EURO' },
2377 $stmt = "WHERE ( user = ?
2378 AND ( ( workhrs > ? AND geo = ? )
2379 OR ( workhrs < ? OR geo = ? ) ) )";
2380 @bind = ('nwiger', '20', 'ASIA', '50', 'EURO');
2382 =head3 Algebraic inconsistency, for historical reasons
2384 C<Important note>: when connecting several conditions, the C<-and->|C<-or>
2385 operator goes C<outside> of the nested structure; whereas when connecting
2386 several constraints on one column, the C<-and> operator goes
2387 C<inside> the arrayref. Here is an example combining both features:
2390 -and => [a => 1, b => 2],
2391 -or => [c => 3, d => 4],
2392 e => [-and => {-like => 'foo%'}, {-like => '%bar'} ]
2397 WHERE ( ( ( a = ? AND b = ? )
2398 OR ( c = ? OR d = ? )
2399 OR ( e LIKE ? AND e LIKE ? ) ) )
2401 This difference in syntax is unfortunate but must be preserved for
2402 historical reasons. So be careful: the two examples below would
2403 seem algebraically equivalent, but they are not
2406 { -like => 'foo%' },
2407 { -like => '%bar' },
2409 # yields: WHERE ( ( col LIKE ? AND col LIKE ? ) )
2412 { col => { -like => 'foo%' } },
2413 { col => { -like => '%bar' } },
2415 # yields: WHERE ( ( col LIKE ? OR col LIKE ? ) )
2418 =head2 Literal SQL and value type operators
2420 The basic premise of SQL::Abstract is that in WHERE specifications the "left
2421 side" is a column name and the "right side" is a value (normally rendered as
2422 a placeholder). This holds true for both hashrefs and arrayref pairs as you
2423 see in the L</WHERE CLAUSES> examples above. Sometimes it is necessary to
2424 alter this behavior. There are several ways of doing so.
2428 This is a virtual operator that signals the string to its right side is an
2429 identifier (a column name) and not a value. For example to compare two
2430 columns you would write:
2433 priority => { '<', 2 },
2434 requestor => { -ident => 'submitter' },
2439 $stmt = "WHERE priority < ? AND requestor = submitter";
2442 If you are maintaining legacy code you may see a different construct as
2443 described in L</Deprecated usage of Literal SQL>, please use C<-ident> in new
2448 This is a virtual operator that signals that the construct to its right side
2449 is a value to be passed to DBI. This is for example necessary when you want
2450 to write a where clause against an array (for RDBMS that support such
2451 datatypes). For example:
2454 array => { -value => [1, 2, 3] }
2459 $stmt = 'WHERE array = ?';
2460 @bind = ([1, 2, 3]);
2462 Note that if you were to simply say:
2468 the result would probably not be what you wanted:
2470 $stmt = 'WHERE array = ? OR array = ? OR array = ?';
2475 Finally, sometimes only literal SQL will do. To include a random snippet
2476 of SQL verbatim, you specify it as a scalar reference. Consider this only
2477 as a last resort. Usually there is a better way. For example:
2480 priority => { '<', 2 },
2481 requestor => { -in => \'(SELECT name FROM hitmen)' },
2486 $stmt = "WHERE priority < ? AND requestor IN (SELECT name FROM hitmen)"
2489 Note that in this example, you only get one bind parameter back, since
2490 the verbatim SQL is passed as part of the statement.
2494 Never use untrusted input as a literal SQL argument - this is a massive
2495 security risk (there is no way to check literal snippets for SQL
2496 injections and other nastyness). If you need to deal with untrusted input
2497 use literal SQL with placeholders as described next.
2499 =head3 Literal SQL with placeholders and bind values (subqueries)
2501 If the literal SQL to be inserted has placeholders and bind values,
2502 use a reference to an arrayref (yes this is a double reference --
2503 not so common, but perfectly legal Perl). For example, to find a date
2504 in Postgres you can use something like this:
2507 date_column => \[ "= date '2008-09-30' - ?::integer", 10 ]
2512 $stmt = "WHERE ( date_column = date '2008-09-30' - ?::integer )"
2515 Note that you must pass the bind values in the same format as they are returned
2516 by L<where|/where(\%where, $order)>. This means that if you set L</bindtype>
2517 to C<columns>, you must provide the bind values in the
2518 C<< [ column_meta => value ] >> format, where C<column_meta> is an opaque
2519 scalar value; most commonly the column name, but you can use any scalar value
2520 (including references and blessed references), L<SQL::Abstract> will simply
2521 pass it through intact. So if C<bindtype> is set to C<columns> the above
2522 example will look like:
2525 date_column => \[ "= date '2008-09-30' - ?::integer", [ {} => 10 ] ]
2528 Literal SQL is especially useful for nesting parenthesized clauses in the
2529 main SQL query. Here is a first example:
2531 my ($sub_stmt, @sub_bind) = ("SELECT c1 FROM t1 WHERE c2 < ? AND c3 LIKE ?",
2535 bar => \["IN ($sub_stmt)" => @sub_bind],
2540 $stmt = "WHERE (foo = ? AND bar IN (SELECT c1 FROM t1
2541 WHERE c2 < ? AND c3 LIKE ?))";
2542 @bind = (1234, 100, "foo%");
2544 Other subquery operators, like for example C<"E<gt> ALL"> or C<"NOT IN">,
2545 are expressed in the same way. Of course the C<$sub_stmt> and
2546 its associated bind values can be generated through a former call
2549 my ($sub_stmt, @sub_bind)
2550 = $sql->select("t1", "c1", {c2 => {"<" => 100},
2551 c3 => {-like => "foo%"}});
2554 bar => \["> ALL ($sub_stmt)" => @sub_bind],
2557 In the examples above, the subquery was used as an operator on a column;
2558 but the same principle also applies for a clause within the main C<%where>
2559 hash, like an EXISTS subquery:
2561 my ($sub_stmt, @sub_bind)
2562 = $sql->select("t1", "*", {c1 => 1, c2 => \"> t0.c0"});
2563 my %where = ( -and => [
2565 \["EXISTS ($sub_stmt)" => @sub_bind],
2570 $stmt = "WHERE (foo = ? AND EXISTS (SELECT * FROM t1
2571 WHERE c1 = ? AND c2 > t0.c0))";
2575 Observe that the condition on C<c2> in the subquery refers to
2576 column C<t0.c0> of the main query: this is I<not> a bind
2577 value, so we have to express it through a scalar ref.
2578 Writing C<< c2 => {">" => "t0.c0"} >> would have generated
2579 C<< c2 > ? >> with bind value C<"t0.c0"> ... not exactly
2580 what we wanted here.
2582 Finally, here is an example where a subquery is used
2583 for expressing unary negation:
2585 my ($sub_stmt, @sub_bind)
2586 = $sql->where({age => [{"<" => 10}, {">" => 20}]});
2587 $sub_stmt =~ s/^ where //i; # don't want "WHERE" in the subclause
2589 lname => {like => '%son%'},
2590 \["NOT ($sub_stmt)" => @sub_bind],
2595 $stmt = "lname LIKE ? AND NOT ( age < ? OR age > ? )"
2596 @bind = ('%son%', 10, 20)
2598 =head3 Deprecated usage of Literal SQL
2600 Below are some examples of archaic use of literal SQL. It is shown only as
2601 reference for those who deal with legacy code. Each example has a much
2602 better, cleaner and safer alternative that users should opt for in new code.
2608 my %where = ( requestor => \'IS NOT NULL' )
2610 $stmt = "WHERE requestor IS NOT NULL"
2612 This used to be the way of generating NULL comparisons, before the handling
2613 of C<undef> got formalized. For new code please use the superior syntax as
2614 described in L</Tests for NULL values>.
2618 my %where = ( requestor => \'= submitter' )
2620 $stmt = "WHERE requestor = submitter"
2622 This used to be the only way to compare columns. Use the superior L</-ident>
2623 method for all new code. For example an identifier declared in such a way
2624 will be properly quoted if L</quote_char> is properly set, while the legacy
2625 form will remain as supplied.
2629 my %where = ( is_ready => \"", completed => { '>', '2012-12-21' } )
2631 $stmt = "WHERE completed > ? AND is_ready"
2632 @bind = ('2012-12-21')
2634 Using an empty string literal used to be the only way to express a boolean.
2635 For all new code please use the much more readable
2636 L<-bool|/Unary operators: bool> operator.
2642 These pages could go on for a while, since the nesting of the data
2643 structures this module can handle are pretty much unlimited (the
2644 module implements the C<WHERE> expansion as a recursive function
2645 internally). Your best bet is to "play around" with the module a
2646 little to see how the data structures behave, and choose the best
2647 format for your data based on that.
2649 And of course, all the values above will probably be replaced with
2650 variables gotten from forms or the command line. After all, if you
2651 knew everything ahead of time, you wouldn't have to worry about
2652 dynamically-generating SQL and could just hardwire it into your
2655 =head1 ORDER BY CLAUSES
2657 Some functions take an order by clause. This can either be a scalar (just a
2658 column name), a hashref of C<< { -desc => 'col' } >> or C<< { -asc => 'col' }
2659 >>, a scalarref, an arrayref-ref, or an arrayref of any of the previous
2662 Given | Will Generate
2663 ---------------------------------------------------------------
2665 'colA' | ORDER BY colA
2667 [qw/colA colB/] | ORDER BY colA, colB
2669 {-asc => 'colA'} | ORDER BY colA ASC
2671 {-desc => 'colB'} | ORDER BY colB DESC
2673 ['colA', {-asc => 'colB'}] | ORDER BY colA, colB ASC
2675 { -asc => [qw/colA colB/] } | ORDER BY colA ASC, colB ASC
2677 \'colA DESC' | ORDER BY colA DESC
2679 \[ 'FUNC(colA, ?)', $x ] | ORDER BY FUNC(colA, ?)
2680 | /* ...with $x bound to ? */
2683 { -asc => 'colA' }, | colA ASC,
2684 { -desc => [qw/colB/] }, | colB DESC,
2685 { -asc => [qw/colC colD/] },| colC ASC, colD ASC,
2686 \'colE DESC', | colE DESC,
2687 \[ 'FUNC(colF, ?)', $x ], | FUNC(colF, ?)
2688 ] | /* ...with $x bound to ? */
2689 ===============================================================
2693 =head1 SPECIAL OPERATORS
2695 my $sqlmaker = SQL::Abstract->new(special_ops => [
2699 my ($self, $field, $op, $arg) = @_;
2705 handler => 'method_name',
2709 A "special operator" is a SQL syntactic clause that can be
2710 applied to a field, instead of a usual binary operator.
2713 WHERE field IN (?, ?, ?)
2714 WHERE field BETWEEN ? AND ?
2715 WHERE MATCH(field) AGAINST (?, ?)
2717 Special operators IN and BETWEEN are fairly standard and therefore
2718 are builtin within C<SQL::Abstract> (as the overridable methods
2719 C<_where_field_IN> and C<_where_field_BETWEEN>). For other operators,
2720 like the MATCH .. AGAINST example above which is specific to MySQL,
2721 you can write your own operator handlers - supply a C<special_ops>
2722 argument to the C<new> method. That argument takes an arrayref of
2723 operator definitions; each operator definition is a hashref with two
2730 the regular expression to match the operator
2734 Either a coderef or a plain scalar method name. In both cases
2735 the expected return is C<< ($sql, @bind) >>.
2737 When supplied with a method name, it is simply called on the
2738 L<SQL::Abstract> object as:
2740 $self->$method_name($field, $op, $arg)
2744 $field is the LHS of the operator
2745 $op is the part that matched the handler regex
2748 When supplied with a coderef, it is called as:
2750 $coderef->($self, $field, $op, $arg)
2755 For example, here is an implementation
2756 of the MATCH .. AGAINST syntax for MySQL
2758 my $sqlmaker = SQL::Abstract->new(special_ops => [
2760 # special op for MySql MATCH (field) AGAINST(word1, word2, ...)
2761 {regex => qr/^match$/i,
2763 my ($self, $field, $op, $arg) = @_;
2764 $arg = [$arg] if not ref $arg;
2765 my $label = $self->_quote($field);
2766 my ($placeholder) = $self->_convert('?');
2767 my $placeholders = join ", ", (($placeholder) x @$arg);
2768 my $sql = $self->_sqlcase('match') . " ($label) "
2769 . $self->_sqlcase('against') . " ($placeholders) ";
2770 my @bind = $self->_bindtype($field, @$arg);
2771 return ($sql, @bind);
2778 =head1 UNARY OPERATORS
2780 my $sqlmaker = SQL::Abstract->new(unary_ops => [
2784 my ($self, $op, $arg) = @_;
2790 handler => 'method_name',
2794 A "unary operator" is a SQL syntactic clause that can be
2795 applied to a field - the operator goes before the field
2797 You can write your own operator handlers - supply a C<unary_ops>
2798 argument to the C<new> method. That argument takes an arrayref of
2799 operator definitions; each operator definition is a hashref with two
2806 the regular expression to match the operator
2810 Either a coderef or a plain scalar method name. In both cases
2811 the expected return is C<< $sql >>.
2813 When supplied with a method name, it is simply called on the
2814 L<SQL::Abstract> object as:
2816 $self->$method_name($op, $arg)
2820 $op is the part that matched the handler regex
2821 $arg is the RHS or argument of the operator
2823 When supplied with a coderef, it is called as:
2825 $coderef->($self, $op, $arg)
2833 Thanks to some benchmarking by Mark Stosberg, it turns out that
2834 this module is many orders of magnitude faster than using C<DBIx::Abstract>.
2835 I must admit this wasn't an intentional design issue, but it's a
2836 byproduct of the fact that you get to control your C<DBI> handles
2839 To maximize performance, use a code snippet like the following:
2841 # prepare a statement handle using the first row
2842 # and then reuse it for the rest of the rows
2844 for my $href (@array_of_hashrefs) {
2845 $stmt ||= $sql->insert('table', $href);
2846 $sth ||= $dbh->prepare($stmt);
2847 $sth->execute($sql->values($href));
2850 The reason this works is because the keys in your C<$href> are sorted
2851 internally by B<SQL::Abstract>. Thus, as long as your data retains
2852 the same structure, you only have to generate the SQL the first time
2853 around. On subsequent queries, simply use the C<values> function provided
2854 by this module to return your values in the correct order.
2856 However this depends on the values having the same type - if, for
2857 example, the values of a where clause may either have values
2858 (resulting in sql of the form C<column = ?> with a single bind
2859 value), or alternatively the values might be C<undef> (resulting in
2860 sql of the form C<column IS NULL> with no bind value) then the
2861 caching technique suggested will not work.
2865 If you use my C<CGI::FormBuilder> module at all, you'll hopefully
2866 really like this part (I do, at least). Building up a complex query
2867 can be as simple as the following:
2874 use CGI::FormBuilder;
2877 my $form = CGI::FormBuilder->new(...);
2878 my $sql = SQL::Abstract->new;
2880 if ($form->submitted) {
2881 my $field = $form->field;
2882 my $id = delete $field->{id};
2883 my($stmt, @bind) = $sql->update('table', $field, {id => $id});
2886 Of course, you would still have to connect using C<DBI> to run the
2887 query, but the point is that if you make your form look like your
2888 table, the actual query script can be extremely simplistic.
2890 If you're B<REALLY> lazy (I am), check out C<HTML::QuickTable> for
2891 a fast interface to returning and formatting data. I frequently
2892 use these three modules together to write complex database query
2893 apps in under 50 lines.
2895 =head1 HOW TO CONTRIBUTE
2897 Contributions are always welcome, in all usable forms (we especially
2898 welcome documentation improvements). The delivery methods include git-
2899 or unified-diff formatted patches, GitHub pull requests, or plain bug
2900 reports either via RT or the Mailing list. Contributors are generally
2901 granted full access to the official repository after their first several
2902 patches pass successful review.
2904 This project is maintained in a git repository. The code and related tools are
2905 accessible at the following locations:
2909 =item * Official repo: L<git://git.shadowcat.co.uk/dbsrgits/SQL-Abstract.git>
2911 =item * Official gitweb: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits/SQL-Abstract.git>
2913 =item * GitHub mirror: L<https://github.com/dbsrgits/sql-abstract>
2915 =item * Authorized committers: L<ssh://dbsrgits@git.shadowcat.co.uk/SQL-Abstract.git>
2921 Version 1.50 was a major internal refactoring of C<SQL::Abstract>.
2922 Great care has been taken to preserve the I<published> behavior
2923 documented in previous versions in the 1.* family; however,
2924 some features that were previously undocumented, or behaved
2925 differently from the documentation, had to be changed in order
2926 to clarify the semantics. Hence, client code that was relying
2927 on some dark areas of C<SQL::Abstract> v1.*
2928 B<might behave differently> in v1.50.
2930 The main changes are:
2936 support for literal SQL through the C<< \ [ $sql, @bind ] >> syntax.
2940 support for the { operator => \"..." } construct (to embed literal SQL)
2944 support for the { operator => \["...", @bind] } construct (to embed literal SQL with bind values)
2948 optional support for L<array datatypes|/"Inserting and Updating Arrays">
2952 defensive programming: check arguments
2956 fixed bug with global logic, which was previously implemented
2957 through global variables yielding side-effects. Prior versions would
2958 interpret C<< [ {cond1, cond2}, [cond3, cond4] ] >>
2959 as C<< "(cond1 AND cond2) OR (cond3 AND cond4)" >>.
2960 Now this is interpreted
2961 as C<< "(cond1 AND cond2) OR (cond3 OR cond4)" >>.
2966 fixed semantics of _bindtype on array args
2970 dropped the C<_anoncopy> of the %where tree. No longer necessary,
2971 we just avoid shifting arrays within that tree.
2975 dropped the C<_modlogic> function
2979 =head1 ACKNOWLEDGEMENTS
2981 There are a number of individuals that have really helped out with
2982 this module. Unfortunately, most of them submitted bugs via CPAN
2983 so I have no idea who they are! But the people I do know are:
2985 Ash Berlin (order_by hash term support)
2986 Matt Trout (DBIx::Class support)
2987 Mark Stosberg (benchmarking)
2988 Chas Owens (initial "IN" operator support)
2989 Philip Collins (per-field SQL functions)
2990 Eric Kolve (hashref "AND" support)
2991 Mike Fragassi (enhancements to "BETWEEN" and "LIKE")
2992 Dan Kubb (support for "quote_char" and "name_sep")
2993 Guillermo Roditi (patch to cleanup "IN" and "BETWEEN", fix and tests for _order_by)
2994 Laurent Dami (internal refactoring, extensible list of special operators, literal SQL)
2995 Norbert Buchmuller (support for literal SQL in hashpair, misc. fixes & tests)
2996 Peter Rabbitson (rewrite of SQLA::Test, misc. fixes & tests)
2997 Oliver Charles (support for "RETURNING" after "INSERT")
3003 L<DBIx::Class>, L<DBIx::Abstract>, L<CGI::FormBuilder>, L<HTML::QuickTable>.
3007 Copyright (c) 2001-2007 Nathan Wiger <nwiger@cpan.org>. All Rights Reserved.
3009 This module is actively maintained by Matt Trout <mst@shadowcatsystems.co.uk>
3011 For support, your best bet is to try the C<DBIx::Class> users mailing list.
3012 While not an official support venue, C<DBIx::Class> makes heavy use of
3013 C<SQL::Abstract>, and as such list members there are very familiar with
3014 how to create queries.
3018 This module is free software; you may copy this under the same
3019 terms as perl itself (either the GNU General Public License or
3020 the Artistic License)