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) = @_;
514 local $self->{convert_where} = $self->{convert};
517 my ($sql, @bind) = defined($where)
518 ? $self->_recurse_where($where)
520 $sql = (defined $sql and length $sql) ? $self->_sqlcase(' where ') . "( $sql )" : '';
524 my ($order_sql, @order_bind) = $self->_order_by($order);
526 push @bind, @order_bind;
529 return wantarray ? ($sql, @bind) : $sql;
533 my ($self, $expr, $logic, $default_scalar_to) = @_;
534 local our $Default_Scalar_To = $default_scalar_to if $default_scalar_to;
535 return undef unless defined($expr);
536 if (ref($expr) eq 'HASH') {
537 if (keys %$expr > 1) {
541 map $self->_expand_expr_hashpair($_ => $expr->{$_}, $logic),
545 return unless %$expr;
546 return $self->_expand_expr_hashpair(%$expr, $logic);
548 if (ref($expr) eq 'ARRAY') {
549 my $logic = lc($logic || $self->{logic});
550 $logic eq 'and' or $logic eq 'or' or puke "unknown logic: $logic";
556 while (my ($el) = splice @expr, 0, 1) {
557 puke "Supplying an empty left hand side argument is not supported in array-pairs"
558 unless defined($el) and length($el);
559 my $elref = ref($el);
561 push(@res, $self->_expand_expr({ $el, shift(@expr) }));
562 } elsif ($elref eq 'ARRAY') {
563 push(@res, $self->_expand_expr($el)) if @$el;
564 } elsif (my $l = is_literal_value($el)) {
565 push @res, { -literal => $l };
566 } elsif ($elref eq 'HASH') {
567 push @res, $self->_expand_expr($el);
572 return { -op => [ $logic, @res ] };
574 if (my $literal = is_literal_value($expr)) {
575 return +{ -literal => $literal };
577 if (!ref($expr) or Scalar::Util::blessed($expr)) {
578 if (my $d = $Default_Scalar_To) {
579 return +{ $d => $expr };
581 if (my $m = our $Cur_Col_Meta) {
582 return +{ -bind => [ $m, $expr ] };
584 return +{ -value => $expr };
589 sub _expand_expr_hashpair {
590 my ($self, $k, $v, $logic) = @_;
591 unless (defined($k) and length($k)) {
592 if (defined($k) and my $literal = is_literal_value($v)) {
593 belch 'Hash-pairs consisting of an empty string with a literal are deprecated, and will be removed in 2.0: use -and => [ $literal ] instead';
594 return { -literal => $literal };
596 puke "Supplying an empty left hand side argument is not supported";
599 $self->_assert_pass_injection_guard($k =~ /^-(.*)$/s);
600 if ($k =~ s/ [_\s]? \d+ $//x ) {
601 belch 'Use of [and|or|nest]_N modifiers is deprecated and will be removed in SQLA v2.0. '
602 . "You probably wanted ...-and => [ $k => COND1, $k => COND2 ... ]";
605 return $self->_expand_expr($v);
609 return $self->_expand_expr($v);
611 puke "-bool => undef not supported" unless defined($v);
612 return { -ident => $v };
615 return { -op => [ 'not', $self->_expand_expr($v) ] };
617 if (my ($rest) = $k =~/^-not[_ ](.*)$/) {
620 $self->_expand_expr_hashpair("-${rest}", $v, $logic)
623 if (my ($logic) = $k =~ /^-(and|or)$/i) {
624 if (ref($v) eq 'HASH') {
625 return $self->_expand_expr($v, $logic);
627 if (ref($v) eq 'ARRAY') {
628 return $self->_expand_expr($v, $logic);
633 $op =~ s/^-// if length($op) > 1;
635 # top level special ops are illegal in general
636 puke "Illegal use of top-level '-$op'"
637 if List::Util::first { $op =~ $_->{regex} } @{$self->{special_ops}};
639 if ($k eq '-value' and my $m = our $Cur_Col_Meta) {
640 return +{ -bind => [ $m, $v ] };
642 if ($k eq '-op' or $k eq '-ident' or $k eq '-value' or $k eq '-bind' or $k eq '-literal' or $k eq '-func') {
645 if (my $custom = $self->{custom_expansions}{($k =~ /^-(.*)$/)[0]}) {
646 return $self->$custom($v);
651 and (keys %$v)[0] =~ /^-/
653 my ($func) = $k =~ /^-(.*)$/;
654 return +{ -func => [ $func, $self->_expand_expr($v) ] };
656 if (!ref($v) or is_literal_value($v)) {
657 return +{ -op => [ $k =~ /^-(.*)$/, $self->_expand_expr($v) ] };
664 and exists $v->{-value}
665 and not defined $v->{-value}
668 return $self->_expand_expr_hashpair($k => { $self->{cmp} => undef });
670 if (!ref($v) or Scalar::Util::blessed($v)) {
675 { -bind => [ $k, $v ] }
679 if (ref($v) eq 'HASH') {
683 map $self->_expand_expr_hashpair($k => { $_ => $v->{$_} }),
690 $self->_assert_pass_injection_guard($vk);
691 if ($vk =~ s/ [_\s]? \d+ $//x ) {
692 belch 'Use of [and|or|nest]_N modifiers is deprecated and will be removed in SQLA v2.0. '
693 . "You probably wanted ...-and => [ -$vk => COND1, -$vk => COND2 ... ]";
695 if ($vk =~ /^(?:not[ _])?between$/) {
696 local our $Cur_Col_Meta = $k;
697 my @rhs = map $self->_expand_expr($_),
698 ref($vv) eq 'ARRAY' ? @$vv : $vv;
700 (@rhs == 1 and ref($rhs[0]) eq 'HASH' and $rhs[0]->{-literal})
702 (@rhs == 2 and defined($rhs[0]) and defined($rhs[1]))
704 puke "Operator '${\uc($vk)}' requires either an arrayref with two defined values or expressions, or a single literal scalarref/arrayref-ref";
707 join(' ', split '_', $vk),
712 if ($vk =~ /^(?:not[ _])?in$/) {
713 if (my $literal = is_literal_value($vv)) {
714 my ($sql, @bind) = @$literal;
715 my $opened_sql = $self->_open_outer_paren($sql);
717 $vk, { -ident => $k },
718 [ { -literal => [ $opened_sql, @bind ] } ]
722 'SQL::Abstract before v1.75 used to generate incorrect SQL when the '
723 . "-${\uc($vk)} operator was given an undef-containing list: !!!AUDIT YOUR CODE "
724 . 'AND DATA!!! (the upcoming Data::Query-based version of SQL::Abstract '
725 . 'will emit the logically correct SQL instead of raising this exception)'
727 puke("Argument passed to the '${\uc($vk)}' operator can not be undefined")
729 my @rhs = map $self->_expand_expr($_),
730 map { ref($_) ? $_ : { -bind => [ $k, $_ ] } }
731 map { defined($_) ? $_: puke($undef_err) }
732 (ref($vv) eq 'ARRAY' ? @$vv : $vv);
733 return $self->${\($vk =~ /^not/ ? 'sqltrue' : 'sqlfalse')} unless @rhs;
736 join(' ', split '_', $vk),
741 if ($vk eq 'ident') {
742 if (! defined $vv or ref $vv) {
743 puke "-$vk requires a single plain scalar argument (a quotable identifier)";
751 if ($vk eq 'value') {
752 return $self->_expand_expr_hashpair($k, undef) unless defined($vv);
756 { -bind => [ $k, $vv ] }
759 if ($vk =~ /^is(?:[ _]not)?$/) {
760 puke "$vk can only take undef as argument"
764 and exists($vv->{-value})
765 and !defined($vv->{-value})
768 return +{ -op => [ $vk.' null', { -ident => $k } ] };
770 if ($vk =~ /^(and|or)$/) {
771 if (ref($vv) eq 'HASH') {
774 map $self->_expand_expr_hashpair($k, { $_ => $vv->{$_} }),
779 if (my $us = List::Util::first { $vk =~ $_->{regex} } @{$self->{user_special_ops}}) {
780 return { -op => [ $vk, { -ident => $k }, $vv ] };
782 if (ref($vv) eq 'ARRAY') {
783 my ($logic, @values) = (
784 (defined($vv->[0]) and $vv->[0] =~ /^-(and|or)$/i)
789 $vk =~ $self->{inequality_op}
790 or join(' ', split '_', $vk) =~ $self->{not_like_op}
792 if (lc($logic) eq '-or' and @values > 1) {
793 my $op = uc join ' ', split '_', $vk;
794 belch "A multi-element arrayref as an argument to the inequality op '$op' "
795 . 'is technically equivalent to an always-true 1=1 (you probably wanted '
796 . "to say ...{ \$inequality_op => [ -and => \@values ] }... instead)"
801 # try to DWIM on equality operators
802 my $op = join ' ', split '_', $vk;
804 $op =~ $self->{equality_op} ? $self->sqlfalse
805 : $op =~ $self->{like_op} ? belch("Supplying an empty arrayref to '@{[ uc $op]}' is deprecated") && $self->sqlfalse
806 : $op =~ $self->{inequality_op} ? $self->sqltrue
807 : $op =~ $self->{not_like_op} ? belch("Supplying an empty arrayref to '@{[ uc $op]}' is deprecated") && $self->sqltrue
808 : puke "operator '$op' applied on an empty array (field '$k')";
812 map $self->_expand_expr_hashpair($k => { $vk => $_ }),
820 and exists $vv->{-value}
821 and not defined $vv->{-value}
824 my $op = join ' ', split '_', $vk;
826 $op =~ /^not$/i ? 'is not' # legacy
827 : $op =~ $self->{equality_op} ? 'is'
828 : $op =~ $self->{like_op} ? belch("Supplying an undefined argument to '@{[ uc $op]}' is deprecated") && 'is'
829 : $op =~ $self->{inequality_op} ? 'is not'
830 : $op =~ $self->{not_like_op} ? belch("Supplying an undefined argument to '@{[ uc $op]}' is deprecated") && 'is not'
831 : puke "unexpected operator '$op' with undef operand";
832 return +{ -op => [ $is.' null', { -ident => $k } ] };
834 local our $Cur_Col_Meta = $k;
838 $self->_expand_expr($vv)
841 if (ref($v) eq 'ARRAY') {
842 return $self->sqlfalse unless @$v;
843 $self->_debug("ARRAY($k) means distribute over elements");
845 $v->[0] =~ /^-((?:and|or))$/i
846 ? ($v = [ @{$v}[1..$#$v] ], $1)
847 : ($self->{logic} || 'or')
851 map $self->_expand_expr({ $k => $_ }, $this_logic), @$v
854 if (my $literal = is_literal_value($v)) {
856 belch 'Hash-pairs consisting of an empty string with a literal are deprecated, and will be removed in 2.0: use -and => [ $literal ] instead';
859 my ($sql, @bind) = @$literal;
860 if ($self->{bindtype} eq 'columns') {
862 if (!defined $_ || ref($_) ne 'ARRAY' || @$_ != 2) {
863 puke "bindtype 'columns' selected, you need to pass: [column_name => bind_value]"
867 return +{ -literal => [ $self->_quote($k).' '.$sql, @bind ] };
873 my ($self, $expr) = @_;
874 my ($k, $v, @rest) = %$expr;
876 my %op = map +("-$_" => '_render_'.$_),
877 qw(op func value bind ident literal);
878 if (my $meth = $op{$k}) {
879 return $self->$meth($v);
881 die "notreached: $k";
885 my ($self, $where, $logic) = @_;
887 #print STDERR Data::Dumper::Concise::Dumper([ $where, $logic ]);
889 my $where_exp = $self->_expand_expr($where, $logic);
891 #print STDERR Data::Dumper::Concise::Dumper([ EXP => $where_exp ]);
893 # dispatch on appropriate method according to refkind of $where
894 # my $method = $self->_METHOD_FOR_refkind("_where", $where_exp);
896 # my ($sql, @bind) = $self->$method($where_exp, $logic);
898 my ($sql, @bind) = defined($where_exp) ? $self->_render_expr($where_exp) : (undef);
900 # DBIx::Class used to call _recurse_where in scalar context
901 # something else might too...
903 return ($sql, @bind);
906 belch "Calling _recurse_where in scalar context is deprecated and will go away before 2.0";
912 my ($self, $ident) = @_;
914 return $self->_convert($self->_quote($ident));
918 my ($self, $value) = @_;
920 return ($self->_convert('?'), $self->_bindtype(undef, $value));
923 my %unop_postfix = map +($_ => 1),
924 'is null', 'is not null',
932 my ($self, $args) = @_;
933 my ($left, $low, $high) = @$args;
934 my ($rhsql, @rhbind) = do {
936 puke "Single arg to between must be a literal"
937 unless $low->{-literal};
940 my ($l, $h) = map [ $self->_render_expr($_) ], $low, $high;
941 (join(' ', $l->[0], $self->_sqlcase('and'), $h->[0]),
942 @{$l}[1..$#$l], @{$h}[1..$#$h])
945 my ($lhsql, @lhbind) = $self->_render_expr($left);
947 join(' ', '(', $lhsql, $self->_sqlcase($op), $rhsql, ')'),
951 }), 'between', 'not between'),
955 my ($self, $args) = @_;
956 my ($lhs, $rhs) = @$args;
959 my ($sql, @bind) = $self->_render_expr($_);
960 push @in_bind, @bind;
963 my ($lhsql, @lbind) = $self->_render_expr($lhs);
965 $lhsql.' '.$self->_sqlcase($op).' ( '
976 my ($op, @args) = @$v;
977 $op =~ s/^-// if length($op) > 1;
979 if (my $h = $special{$op}) {
980 return $self->$h(\@args);
982 if (my $us = List::Util::first { $op =~ $_->{regex} } @{$self->{user_special_ops}}) {
983 puke "Special op '${op}' requires first value to be identifier"
984 unless my ($k) = map $_->{-ident}, grep ref($_) eq 'HASH', $args[0];
985 return $self->${\($us->{handler})}($k, $op, $args[1]);
987 my $final_op = $op =~ /^(?:is|not)_/ ? join(' ', split '_', $op) : $op;
988 if (@args == 1 and $op !~ /^(and|or)$/) {
989 my ($expr_sql, @bind) = $self->_render_expr($args[0]);
990 my $op_sql = $self->_sqlcase($final_op);
992 $unop_postfix{lc($final_op)}
993 ? "${expr_sql} ${op_sql}"
994 : "${op_sql} ${expr_sql}"
996 return (($op eq 'not' ? '('.$final_sql.')' : $final_sql), @bind);
998 my @parts = map [ $self->_render_expr($_) ], @args;
999 my ($final_sql) = map +($op =~ /^(and|or)$/ ? "(${_})" : $_), join(
1000 ($final_op eq ',' ? '' : ' ').$self->_sqlcase($final_op).' ',
1005 map @{$_}[1..$#$_], @parts
1012 my ($self, $rest) = @_;
1013 my ($func, @args) = @$rest;
1017 push @arg_sql, shift @x;
1019 } map [ $self->_render_expr($_) ], @args;
1020 return ($self->_sqlcase($func).'('.join(', ', @arg_sql).')', @bind);
1024 my ($self, $bind) = @_;
1025 return ($self->_convert('?'), $self->_bindtype(@$bind));
1028 sub _render_literal {
1029 my ($self, $literal) = @_;
1030 $self->_assert_bindval_matches_bindtype(@{$literal}[1..$#$literal]);
1034 # Some databases (SQLite) treat col IN (1, 2) different from
1035 # col IN ( (1, 2) ). Use this to strip all outer parens while
1036 # adding them back in the corresponding method
1037 sub _open_outer_paren {
1038 my ($self, $sql) = @_;
1040 while (my ($inner) = $sql =~ /^ \s* \( (.*) \) \s* $/xs) {
1042 # there are closing parens inside, need the heavy duty machinery
1043 # to reevaluate the extraction starting from $sql (full reevaluation)
1044 if ($inner =~ /\)/) {
1045 require Text::Balanced;
1047 my (undef, $remainder) = do {
1048 # idiotic design - writes to $@ but *DOES NOT* throw exceptions
1050 Text::Balanced::extract_bracketed($sql, '()', qr/\s*/);
1053 # the entire expression needs to be a balanced bracketed thing
1054 # (after an extract no remainder sans trailing space)
1055 last if defined $remainder and $remainder =~ /\S/;
1065 #======================================================================
1067 #======================================================================
1070 my ($self, $arg) = @_;
1072 return '' unless defined($arg) and not (ref($arg) eq 'ARRAY' and !@$arg);
1074 my $expander = sub {
1075 my ($self, $dir, $expr) = @_;
1076 my @exp = map +(defined($dir) ? { -op => [ $dir => $_ ] } : $_),
1077 map $self->_expand_expr($_, undef, -ident),
1078 ref($expr) eq 'ARRAY' ? @$expr : $expr;
1079 return (@exp > 1 ? { -op => [ ',', @exp ] } : $exp[0]);
1082 local $self->{custom_expansions} = {
1083 asc => sub { shift->$expander(asc => @_) },
1084 desc => sub { shift->$expander(desc => @_) },
1087 my $expanded = $self->$expander(undef, $arg);
1089 my ($sql, @bind) = $self->_render_expr($expanded);
1091 my $final_sql = $self->_sqlcase(' order by ').$sql;
1093 return wantarray ? ($final_sql, @bind) : $final_sql;
1096 #======================================================================
1097 # DATASOURCE (FOR NOW, JUST PLAIN TABLE OR LIST OF TABLES)
1098 #======================================================================
1103 ($self->_render_expr(
1104 $self->_expand_maybe_list_expr($from, undef, -ident)
1109 #======================================================================
1111 #======================================================================
1113 sub _expand_maybe_list_expr {
1114 my ($self, $expr, $logic, $default) = @_;
1115 return ref($expr) eq 'ARRAY'
1117 ',', map $self->_expand_expr($_, $logic, $default), @$expr
1119 : $self->_expand_expr($expr, $logic, $default);
1122 # highly optimized, as it's called way too often
1124 # my ($self, $label) = @_;
1126 return '' unless defined $_[1];
1127 return ${$_[1]} if ref($_[1]) eq 'SCALAR';
1129 $_[0]->{quote_char} or
1130 ($_[0]->_assert_pass_injection_guard($_[1]), return $_[1]);
1132 my $qref = ref $_[0]->{quote_char};
1134 !$qref ? ($_[0]->{quote_char}, $_[0]->{quote_char})
1135 : ($qref eq 'ARRAY') ? @{$_[0]->{quote_char}}
1136 : puke "Unsupported quote_char format: $_[0]->{quote_char}";
1138 my $esc = $_[0]->{escape_char} || $r;
1140 # parts containing * are naturally unquoted
1141 return join($_[0]->{name_sep}||'', map
1142 +( $_ eq '*' ? $_ : do { (my $n = $_) =~ s/(\Q$esc\E|\Q$r\E)/$esc$1/g; $l . $n . $r } ),
1143 ( $_[0]->{name_sep} ? split (/\Q$_[0]->{name_sep}\E/, $_[1] ) : $_[1] )
1148 # Conversion, if applicable
1150 #my ($self, $arg) = @_;
1151 if ($_[0]->{convert_where}) {
1152 return $_[0]->_sqlcase($_[0]->{convert_where}) .'(' . $_[1] . ')';
1159 #my ($self, $col, @vals) = @_;
1160 # called often - tighten code
1161 return $_[0]->{bindtype} eq 'columns'
1162 ? map {[$_[1], $_]} @_[2 .. $#_]
1167 # Dies if any element of @bind is not in [colname => value] format
1168 # if bindtype is 'columns'.
1169 sub _assert_bindval_matches_bindtype {
1170 # my ($self, @bind) = @_;
1172 if ($self->{bindtype} eq 'columns') {
1174 if (!defined $_ || ref($_) ne 'ARRAY' || @$_ != 2) {
1175 puke "bindtype 'columns' selected, you need to pass: [column_name => bind_value]"
1181 sub _join_sql_clauses {
1182 my ($self, $logic, $clauses_aref, $bind_aref) = @_;
1184 if (@$clauses_aref > 1) {
1185 my $join = " " . $self->_sqlcase($logic) . " ";
1186 my $sql = '( ' . join($join, @$clauses_aref) . ' )';
1187 return ($sql, @$bind_aref);
1189 elsif (@$clauses_aref) {
1190 return ($clauses_aref->[0], @$bind_aref); # no parentheses
1193 return (); # if no SQL, ignore @$bind_aref
1198 # Fix SQL case, if so requested
1200 # LDNOTE: if $self->{case} is true, then it contains 'lower', so we
1201 # don't touch the argument ... crooked logic, but let's not change it!
1202 return $_[0]->{case} ? $_[1] : uc($_[1]);
1206 #======================================================================
1207 # DISPATCHING FROM REFKIND
1208 #======================================================================
1211 my ($self, $data) = @_;
1213 return 'UNDEF' unless defined $data;
1215 # blessed objects are treated like scalars
1216 my $ref = (Scalar::Util::blessed $data) ? '' : ref $data;
1218 return 'SCALAR' unless $ref;
1221 while ($ref eq 'REF') {
1223 $ref = (Scalar::Util::blessed $data) ? '' : ref $data;
1227 return ($ref||'SCALAR') . ('REF' x $n_steps);
1231 my ($self, $data) = @_;
1232 my @try = ($self->_refkind($data));
1233 push @try, 'SCALAR_or_UNDEF' if $try[0] eq 'SCALAR' || $try[0] eq 'UNDEF';
1234 push @try, 'FALLBACK';
1238 sub _METHOD_FOR_refkind {
1239 my ($self, $meth_prefix, $data) = @_;
1242 for (@{$self->_try_refkind($data)}) {
1243 $method = $self->can($meth_prefix."_".$_)
1247 return $method || puke "cannot dispatch on '$meth_prefix' for ".$self->_refkind($data);
1251 sub _SWITCH_refkind {
1252 my ($self, $data, $dispatch_table) = @_;
1255 for (@{$self->_try_refkind($data)}) {
1256 $coderef = $dispatch_table->{$_}
1260 puke "no dispatch entry for ".$self->_refkind($data)
1269 #======================================================================
1270 # VALUES, GENERATE, AUTOLOAD
1271 #======================================================================
1273 # LDNOTE: original code from nwiger, didn't touch code in that section
1274 # I feel the AUTOLOAD stuff should not be the default, it should
1275 # only be activated on explicit demand by user.
1279 my $data = shift || return;
1280 puke "Argument to ", __PACKAGE__, "->values must be a \\%hash"
1281 unless ref $data eq 'HASH';
1284 foreach my $k (sort keys %$data) {
1285 my $v = $data->{$k};
1286 $self->_SWITCH_refkind($v, {
1288 if ($self->{array_datatypes}) { # array datatype
1289 push @all_bind, $self->_bindtype($k, $v);
1291 else { # literal SQL with bind
1292 my ($sql, @bind) = @$v;
1293 $self->_assert_bindval_matches_bindtype(@bind);
1294 push @all_bind, @bind;
1297 ARRAYREFREF => sub { # literal SQL with bind
1298 my ($sql, @bind) = @${$v};
1299 $self->_assert_bindval_matches_bindtype(@bind);
1300 push @all_bind, @bind;
1302 SCALARREF => sub { # literal SQL without bind
1304 SCALAR_or_UNDEF => sub {
1305 push @all_bind, $self->_bindtype($k, $v);
1316 my(@sql, @sqlq, @sqlv);
1320 if ($ref eq 'HASH') {
1321 for my $k (sort keys %$_) {
1324 my $label = $self->_quote($k);
1325 if ($r eq 'ARRAY') {
1326 # literal SQL with bind
1327 my ($sql, @bind) = @$v;
1328 $self->_assert_bindval_matches_bindtype(@bind);
1329 push @sqlq, "$label = $sql";
1331 } elsif ($r eq 'SCALAR') {
1332 # literal SQL without bind
1333 push @sqlq, "$label = $$v";
1335 push @sqlq, "$label = ?";
1336 push @sqlv, $self->_bindtype($k, $v);
1339 push @sql, $self->_sqlcase('set'), join ', ', @sqlq;
1340 } elsif ($ref eq 'ARRAY') {
1341 # unlike insert(), assume these are ONLY the column names, i.e. for SQL
1344 if ($r eq 'ARRAY') { # literal SQL with bind
1345 my ($sql, @bind) = @$v;
1346 $self->_assert_bindval_matches_bindtype(@bind);
1349 } elsif ($r eq 'SCALAR') { # literal SQL without bind
1350 # embedded literal SQL
1357 push @sql, '(' . join(', ', @sqlq) . ')';
1358 } elsif ($ref eq 'SCALAR') {
1362 # strings get case twiddled
1363 push @sql, $self->_sqlcase($_);
1367 my $sql = join ' ', @sql;
1369 # this is pretty tricky
1370 # if ask for an array, return ($stmt, @bind)
1371 # otherwise, s/?/shift @sqlv/ to put it inline
1373 return ($sql, @sqlv);
1375 1 while $sql =~ s/\?/my $d = shift(@sqlv);
1376 ref $d ? $d->[1] : $d/e;
1385 # This allows us to check for a local, then _form, attr
1387 my($name) = $AUTOLOAD =~ /.*::(.+)/;
1388 return $self->generate($name, @_);
1399 SQL::Abstract - Generate SQL from Perl data structures
1405 my $sql = SQL::Abstract->new;
1407 my($stmt, @bind) = $sql->select($source, \@fields, \%where, $order);
1409 my($stmt, @bind) = $sql->insert($table, \%fieldvals || \@values);
1411 my($stmt, @bind) = $sql->update($table, \%fieldvals, \%where);
1413 my($stmt, @bind) = $sql->delete($table, \%where);
1415 # Then, use these in your DBI statements
1416 my $sth = $dbh->prepare($stmt);
1417 $sth->execute(@bind);
1419 # Just generate the WHERE clause
1420 my($stmt, @bind) = $sql->where(\%where, $order);
1422 # Return values in the same order, for hashed queries
1423 # See PERFORMANCE section for more details
1424 my @bind = $sql->values(\%fieldvals);
1428 This module was inspired by the excellent L<DBIx::Abstract>.
1429 However, in using that module I found that what I really wanted
1430 to do was generate SQL, but still retain complete control over my
1431 statement handles and use the DBI interface. So, I set out to
1432 create an abstract SQL generation module.
1434 While based on the concepts used by L<DBIx::Abstract>, there are
1435 several important differences, especially when it comes to WHERE
1436 clauses. I have modified the concepts used to make the SQL easier
1437 to generate from Perl data structures and, IMO, more intuitive.
1438 The underlying idea is for this module to do what you mean, based
1439 on the data structures you provide it. The big advantage is that
1440 you don't have to modify your code every time your data changes,
1441 as this module figures it out.
1443 To begin with, an SQL INSERT is as easy as just specifying a hash
1444 of C<key=value> pairs:
1447 name => 'Jimbo Bobson',
1448 phone => '123-456-7890',
1449 address => '42 Sister Lane',
1450 city => 'St. Louis',
1451 state => 'Louisiana',
1454 The SQL can then be generated with this:
1456 my($stmt, @bind) = $sql->insert('people', \%data);
1458 Which would give you something like this:
1460 $stmt = "INSERT INTO people
1461 (address, city, name, phone, state)
1462 VALUES (?, ?, ?, ?, ?)";
1463 @bind = ('42 Sister Lane', 'St. Louis', 'Jimbo Bobson',
1464 '123-456-7890', 'Louisiana');
1466 These are then used directly in your DBI code:
1468 my $sth = $dbh->prepare($stmt);
1469 $sth->execute(@bind);
1471 =head2 Inserting and Updating Arrays
1473 If your database has array types (like for example Postgres),
1474 activate the special option C<< array_datatypes => 1 >>
1475 when creating the C<SQL::Abstract> object.
1476 Then you may use an arrayref to insert and update database array types:
1478 my $sql = SQL::Abstract->new(array_datatypes => 1);
1480 planets => [qw/Mercury Venus Earth Mars/]
1483 my($stmt, @bind) = $sql->insert('solar_system', \%data);
1487 $stmt = "INSERT INTO solar_system (planets) VALUES (?)"
1489 @bind = (['Mercury', 'Venus', 'Earth', 'Mars']);
1492 =head2 Inserting and Updating SQL
1494 In order to apply SQL functions to elements of your C<%data> you may
1495 specify a reference to an arrayref for the given hash value. For example,
1496 if you need to execute the Oracle C<to_date> function on a value, you can
1497 say something like this:
1501 date_entered => \[ "to_date(?,'MM/DD/YYYY')", "03/02/2003" ],
1504 The first value in the array is the actual SQL. Any other values are
1505 optional and would be included in the bind values array. This gives
1508 my($stmt, @bind) = $sql->insert('people', \%data);
1510 $stmt = "INSERT INTO people (name, date_entered)
1511 VALUES (?, to_date(?,'MM/DD/YYYY'))";
1512 @bind = ('Bill', '03/02/2003');
1514 An UPDATE is just as easy, all you change is the name of the function:
1516 my($stmt, @bind) = $sql->update('people', \%data);
1518 Notice that your C<%data> isn't touched; the module will generate
1519 the appropriately quirky SQL for you automatically. Usually you'll
1520 want to specify a WHERE clause for your UPDATE, though, which is
1521 where handling C<%where> hashes comes in handy...
1523 =head2 Complex where statements
1525 This module can generate pretty complicated WHERE statements
1526 easily. For example, simple C<key=value> pairs are taken to mean
1527 equality, and if you want to see if a field is within a set
1528 of values, you can use an arrayref. Let's say we wanted to
1529 SELECT some data based on this criteria:
1532 requestor => 'inna',
1533 worker => ['nwiger', 'rcwe', 'sfz'],
1534 status => { '!=', 'completed' }
1537 my($stmt, @bind) = $sql->select('tickets', '*', \%where);
1539 The above would give you something like this:
1541 $stmt = "SELECT * FROM tickets WHERE
1542 ( requestor = ? ) AND ( status != ? )
1543 AND ( worker = ? OR worker = ? OR worker = ? )";
1544 @bind = ('inna', 'completed', 'nwiger', 'rcwe', 'sfz');
1546 Which you could then use in DBI code like so:
1548 my $sth = $dbh->prepare($stmt);
1549 $sth->execute(@bind);
1555 The methods are simple. There's one for every major SQL operation,
1556 and a constructor you use first. The arguments are specified in a
1557 similar order for each method (table, then fields, then a where
1558 clause) to try and simplify things.
1560 =head2 new(option => 'value')
1562 The C<new()> function takes a list of options and values, and returns
1563 a new B<SQL::Abstract> object which can then be used to generate SQL
1564 through the methods below. The options accepted are:
1570 If set to 'lower', then SQL will be generated in all lowercase. By
1571 default SQL is generated in "textbook" case meaning something like:
1573 SELECT a_field FROM a_table WHERE some_field LIKE '%someval%'
1575 Any setting other than 'lower' is ignored.
1579 This determines what the default comparison operator is. By default
1580 it is C<=>, meaning that a hash like this:
1582 %where = (name => 'nwiger', email => 'nate@wiger.org');
1584 Will generate SQL like this:
1586 WHERE name = 'nwiger' AND email = 'nate@wiger.org'
1588 However, you may want loose comparisons by default, so if you set
1589 C<cmp> to C<like> you would get SQL such as:
1591 WHERE name like 'nwiger' AND email like 'nate@wiger.org'
1593 You can also override the comparison on an individual basis - see
1594 the huge section on L</"WHERE CLAUSES"> at the bottom.
1596 =item sqltrue, sqlfalse
1598 Expressions for inserting boolean values within SQL statements.
1599 By default these are C<1=1> and C<1=0>. They are used
1600 by the special operators C<-in> and C<-not_in> for generating
1601 correct SQL even when the argument is an empty array (see below).
1605 This determines the default logical operator for multiple WHERE
1606 statements in arrays or hashes. If absent, the default logic is "or"
1607 for arrays, and "and" for hashes. This means that a WHERE
1611 event_date => {'>=', '2/13/99'},
1612 event_date => {'<=', '4/24/03'},
1615 will generate SQL like this:
1617 WHERE event_date >= '2/13/99' OR event_date <= '4/24/03'
1619 This is probably not what you want given this query, though (look
1620 at the dates). To change the "OR" to an "AND", simply specify:
1622 my $sql = SQL::Abstract->new(logic => 'and');
1624 Which will change the above C<WHERE> to:
1626 WHERE event_date >= '2/13/99' AND event_date <= '4/24/03'
1628 The logic can also be changed locally by inserting
1629 a modifier in front of an arrayref:
1631 @where = (-and => [event_date => {'>=', '2/13/99'},
1632 event_date => {'<=', '4/24/03'} ]);
1634 See the L</"WHERE CLAUSES"> section for explanations.
1638 This will automatically convert comparisons using the specified SQL
1639 function for both column and value. This is mostly used with an argument
1640 of C<upper> or C<lower>, so that the SQL will have the effect of
1641 case-insensitive "searches". For example, this:
1643 $sql = SQL::Abstract->new(convert => 'upper');
1644 %where = (keywords => 'MaKe iT CAse inSeNSItive');
1646 Will turn out the following SQL:
1648 WHERE upper(keywords) like upper('MaKe iT CAse inSeNSItive')
1650 The conversion can be C<upper()>, C<lower()>, or any other SQL function
1651 that can be applied symmetrically to fields (actually B<SQL::Abstract> does
1652 not validate this option; it will just pass through what you specify verbatim).
1656 This is a kludge because many databases suck. For example, you can't
1657 just bind values using DBI's C<execute()> for Oracle C<CLOB> or C<BLOB> fields.
1658 Instead, you have to use C<bind_param()>:
1660 $sth->bind_param(1, 'reg data');
1661 $sth->bind_param(2, $lots, {ora_type => ORA_CLOB});
1663 The problem is, B<SQL::Abstract> will normally just return a C<@bind> array,
1664 which loses track of which field each slot refers to. Fear not.
1666 If you specify C<bindtype> in new, you can determine how C<@bind> is returned.
1667 Currently, you can specify either C<normal> (default) or C<columns>. If you
1668 specify C<columns>, you will get an array that looks like this:
1670 my $sql = SQL::Abstract->new(bindtype => 'columns');
1671 my($stmt, @bind) = $sql->insert(...);
1674 [ 'column1', 'value1' ],
1675 [ 'column2', 'value2' ],
1676 [ 'column3', 'value3' ],
1679 You can then iterate through this manually, using DBI's C<bind_param()>.
1681 $sth->prepare($stmt);
1684 my($col, $data) = @$_;
1685 if ($col eq 'details' || $col eq 'comments') {
1686 $sth->bind_param($i, $data, {ora_type => ORA_CLOB});
1687 } elsif ($col eq 'image') {
1688 $sth->bind_param($i, $data, {ora_type => ORA_BLOB});
1690 $sth->bind_param($i, $data);
1694 $sth->execute; # execute without @bind now
1696 Now, why would you still use B<SQL::Abstract> if you have to do this crap?
1697 Basically, the advantage is still that you don't have to care which fields
1698 are or are not included. You could wrap that above C<for> loop in a simple
1699 sub called C<bind_fields()> or something and reuse it repeatedly. You still
1700 get a layer of abstraction over manual SQL specification.
1702 Note that if you set L</bindtype> to C<columns>, the C<\[ $sql, @bind ]>
1703 construct (see L</Literal SQL with placeholders and bind values (subqueries)>)
1704 will expect the bind values in this format.
1708 This is the character that a table or column name will be quoted
1709 with. By default this is an empty string, but you could set it to
1710 the character C<`>, to generate SQL like this:
1712 SELECT `a_field` FROM `a_table` WHERE `some_field` LIKE '%someval%'
1714 Alternatively, you can supply an array ref of two items, the first being the left
1715 hand quote character, and the second the right hand quote character. For
1716 example, you could supply C<['[',']']> for SQL Server 2000 compliant quotes
1717 that generates SQL like this:
1719 SELECT [a_field] FROM [a_table] WHERE [some_field] LIKE '%someval%'
1721 Quoting is useful if you have tables or columns names that are reserved
1722 words in your database's SQL dialect.
1726 This is the character that will be used to escape L</quote_char>s appearing
1727 in an identifier before it has been quoted.
1729 The parameter default in case of a single L</quote_char> character is the quote
1732 When opening-closing-style quoting is used (L</quote_char> is an arrayref)
1733 this parameter defaults to the B<closing (right)> L</quote_char>. Occurrences
1734 of the B<opening (left)> L</quote_char> within the identifier are currently left
1735 untouched. The default for opening-closing-style quotes may change in future
1736 versions, thus you are B<strongly encouraged> to specify the escape character
1741 This is the character that separates a table and column name. It is
1742 necessary to specify this when the C<quote_char> option is selected,
1743 so that tables and column names can be individually quoted like this:
1745 SELECT `table`.`one_field` FROM `table` WHERE `table`.`other_field` = 1
1747 =item injection_guard
1749 A regular expression C<qr/.../> that is applied to any C<-function> and unquoted
1750 column name specified in a query structure. This is a safety mechanism to avoid
1751 injection attacks when mishandling user input e.g.:
1753 my %condition_as_column_value_pairs = get_values_from_user();
1754 $sqla->select( ... , \%condition_as_column_value_pairs );
1756 If the expression matches an exception is thrown. Note that literal SQL
1757 supplied via C<\'...'> or C<\['...']> is B<not> checked in any way.
1759 Defaults to checking for C<;> and the C<GO> keyword (TransactSQL)
1761 =item array_datatypes
1763 When this option is true, arrayrefs in INSERT or UPDATE are
1764 interpreted as array datatypes and are passed directly
1766 When this option is false, arrayrefs are interpreted
1767 as literal SQL, just like refs to arrayrefs
1768 (but this behavior is for backwards compatibility; when writing
1769 new queries, use the "reference to arrayref" syntax
1775 Takes a reference to a list of "special operators"
1776 to extend the syntax understood by L<SQL::Abstract>.
1777 See section L</"SPECIAL OPERATORS"> for details.
1781 Takes a reference to a list of "unary operators"
1782 to extend the syntax understood by L<SQL::Abstract>.
1783 See section L</"UNARY OPERATORS"> for details.
1789 =head2 insert($table, \@values || \%fieldvals, \%options)
1791 This is the simplest function. You simply give it a table name
1792 and either an arrayref of values or hashref of field/value pairs.
1793 It returns an SQL INSERT statement and a list of bind values.
1794 See the sections on L</"Inserting and Updating Arrays"> and
1795 L</"Inserting and Updating SQL"> for information on how to insert
1796 with those data types.
1798 The optional C<\%options> hash reference may contain additional
1799 options to generate the insert SQL. Currently supported options
1806 Takes either a scalar of raw SQL fields, or an array reference of
1807 field names, and adds on an SQL C<RETURNING> statement at the end.
1808 This allows you to return data generated by the insert statement
1809 (such as row IDs) without performing another C<SELECT> statement.
1810 Note, however, this is not part of the SQL standard and may not
1811 be supported by all database engines.
1815 =head2 update($table, \%fieldvals, \%where, \%options)
1817 This takes a table, hashref of field/value pairs, and an optional
1818 hashref L<WHERE clause|/WHERE CLAUSES>. It returns an SQL UPDATE function and a list
1820 See the sections on L</"Inserting and Updating Arrays"> and
1821 L</"Inserting and Updating SQL"> for information on how to insert
1822 with those data types.
1824 The optional C<\%options> hash reference may contain additional
1825 options to generate the update SQL. Currently supported options
1832 See the C<returning> option to
1833 L<insert|/insert($table, \@values || \%fieldvals, \%options)>.
1837 =head2 select($source, $fields, $where, $order)
1839 This returns a SQL SELECT statement and associated list of bind values, as
1840 specified by the arguments:
1846 Specification of the 'FROM' part of the statement.
1847 The argument can be either a plain scalar (interpreted as a table
1848 name, will be quoted), or an arrayref (interpreted as a list
1849 of table names, joined by commas, quoted), or a scalarref
1850 (literal SQL, not quoted).
1854 Specification of the list of fields to retrieve from
1856 The argument can be either an arrayref (interpreted as a list
1857 of field names, will be joined by commas and quoted), or a
1858 plain scalar (literal SQL, not quoted).
1859 Please observe that this API is not as flexible as that of
1860 the first argument C<$source>, for backwards compatibility reasons.
1864 Optional argument to specify the WHERE part of the query.
1865 The argument is most often a hashref, but can also be
1866 an arrayref or plain scalar --
1867 see section L<WHERE clause|/"WHERE CLAUSES"> for details.
1871 Optional argument to specify the ORDER BY part of the query.
1872 The argument can be a scalar, a hashref or an arrayref
1873 -- see section L<ORDER BY clause|/"ORDER BY CLAUSES">
1879 =head2 delete($table, \%where, \%options)
1881 This takes a table name and optional hashref L<WHERE clause|/WHERE CLAUSES>.
1882 It returns an SQL DELETE statement and list of bind values.
1884 The optional C<\%options> hash reference may contain additional
1885 options to generate the delete SQL. Currently supported options
1892 See the C<returning> option to
1893 L<insert|/insert($table, \@values || \%fieldvals, \%options)>.
1897 =head2 where(\%where, $order)
1899 This is used to generate just the WHERE clause. For example,
1900 if you have an arbitrary data structure and know what the
1901 rest of your SQL is going to look like, but want an easy way
1902 to produce a WHERE clause, use this. It returns an SQL WHERE
1903 clause and list of bind values.
1906 =head2 values(\%data)
1908 This just returns the values from the hash C<%data>, in the same
1909 order that would be returned from any of the other above queries.
1910 Using this allows you to markedly speed up your queries if you
1911 are affecting lots of rows. See below under the L</"PERFORMANCE"> section.
1913 =head2 generate($any, 'number', $of, \@data, $struct, \%types)
1915 Warning: This is an experimental method and subject to change.
1917 This returns arbitrarily generated SQL. It's a really basic shortcut.
1918 It will return two different things, depending on return context:
1920 my($stmt, @bind) = $sql->generate('create table', \$table, \@fields);
1921 my $stmt_and_val = $sql->generate('create table', \$table, \@fields);
1923 These would return the following:
1925 # First calling form
1926 $stmt = "CREATE TABLE test (?, ?)";
1927 @bind = (field1, field2);
1929 # Second calling form
1930 $stmt_and_val = "CREATE TABLE test (field1, field2)";
1932 Depending on what you're trying to do, it's up to you to choose the correct
1933 format. In this example, the second form is what you would want.
1937 $sql->generate('alter session', { nls_date_format => 'MM/YY' });
1941 ALTER SESSION SET nls_date_format = 'MM/YY'
1943 You get the idea. Strings get their case twiddled, but everything
1944 else remains verbatim.
1946 =head1 EXPORTABLE FUNCTIONS
1948 =head2 is_plain_value
1950 Determines if the supplied argument is a plain value as understood by this
1955 =item * The value is C<undef>
1957 =item * The value is a non-reference
1959 =item * The value is an object with stringification overloading
1961 =item * The value is of the form C<< { -value => $anything } >>
1965 On failure returns C<undef>, on success returns a B<scalar> reference
1966 to the original supplied argument.
1972 The stringification overloading detection is rather advanced: it takes
1973 into consideration not only the presence of a C<""> overload, but if that
1974 fails also checks for enabled
1975 L<autogenerated versions of C<"">|overload/Magic Autogeneration>, based
1976 on either C<0+> or C<bool>.
1978 Unfortunately testing in the field indicates that this
1979 detection B<< may tickle a latent bug in perl versions before 5.018 >>,
1980 but only when very large numbers of stringifying objects are involved.
1981 At the time of writing ( Sep 2014 ) there is no clear explanation of
1982 the direct cause, nor is there a manageably small test case that reliably
1983 reproduces the problem.
1985 If you encounter any of the following exceptions in B<random places within
1986 your application stack> - this module may be to blame:
1988 Operation "ne": no method found,
1989 left argument in overloaded package <something>,
1990 right argument in overloaded package <something>
1994 Stub found while resolving method "???" overloading """" in package <something>
1996 If you fall victim to the above - please attempt to reduce the problem
1997 to something that could be sent to the L<SQL::Abstract developers
1998 |DBIx::Class/GETTING HELP/SUPPORT>
1999 (either publicly or privately). As a workaround in the meantime you can
2000 set C<$ENV{SQLA_ISVALUE_IGNORE_AUTOGENERATED_STRINGIFICATION}> to a true
2001 value, which will most likely eliminate your problem (at the expense of
2002 not being able to properly detect exotic forms of stringification).
2004 This notice and environment variable will be removed in a future version,
2005 as soon as the underlying problem is found and a reliable workaround is
2010 =head2 is_literal_value
2012 Determines if the supplied argument is a literal value as understood by this
2017 =item * C<\$sql_string>
2019 =item * C<\[ $sql_string, @bind_values ]>
2023 On failure returns C<undef>, on success returns an B<array> reference
2024 containing the unpacked version of the supplied literal SQL and bind values.
2026 =head1 WHERE CLAUSES
2030 This module uses a variation on the idea from L<DBIx::Abstract>. It
2031 is B<NOT>, repeat I<not> 100% compatible. B<The main logic of this
2032 module is that things in arrays are OR'ed, and things in hashes
2035 The easiest way to explain is to show lots of examples. After
2036 each C<%where> hash shown, it is assumed you used:
2038 my($stmt, @bind) = $sql->where(\%where);
2040 However, note that the C<%where> hash can be used directly in any
2041 of the other functions as well, as described above.
2043 =head2 Key-value pairs
2045 So, let's get started. To begin, a simple hash:
2049 status => 'completed'
2052 Is converted to SQL C<key = val> statements:
2054 $stmt = "WHERE user = ? AND status = ?";
2055 @bind = ('nwiger', 'completed');
2057 One common thing I end up doing is having a list of values that
2058 a field can be in. To do this, simply specify a list inside of
2063 status => ['assigned', 'in-progress', 'pending'];
2066 This simple code will create the following:
2068 $stmt = "WHERE user = ? AND ( status = ? OR status = ? OR status = ? )";
2069 @bind = ('nwiger', 'assigned', 'in-progress', 'pending');
2071 A field associated to an empty arrayref will be considered a
2072 logical false and will generate 0=1.
2074 =head2 Tests for NULL values
2076 If the value part is C<undef> then this is converted to SQL <IS NULL>
2085 $stmt = "WHERE user = ? AND status IS NULL";
2088 To test if a column IS NOT NULL:
2092 status => { '!=', undef },
2095 =head2 Specific comparison operators
2097 If you want to specify a different type of operator for your comparison,
2098 you can use a hashref for a given column:
2102 status => { '!=', 'completed' }
2105 Which would generate:
2107 $stmt = "WHERE user = ? AND status != ?";
2108 @bind = ('nwiger', 'completed');
2110 To test against multiple values, just enclose the values in an arrayref:
2112 status => { '=', ['assigned', 'in-progress', 'pending'] };
2114 Which would give you:
2116 "WHERE status = ? OR status = ? OR status = ?"
2119 The hashref can also contain multiple pairs, in which case it is expanded
2120 into an C<AND> of its elements:
2124 status => { '!=', 'completed', -not_like => 'pending%' }
2127 # Or more dynamically, like from a form
2128 $where{user} = 'nwiger';
2129 $where{status}{'!='} = 'completed';
2130 $where{status}{'-not_like'} = 'pending%';
2132 # Both generate this
2133 $stmt = "WHERE user = ? AND status != ? AND status NOT LIKE ?";
2134 @bind = ('nwiger', 'completed', 'pending%');
2137 To get an OR instead, you can combine it with the arrayref idea:
2141 priority => [ { '=', 2 }, { '>', 5 } ]
2144 Which would generate:
2146 $stmt = "WHERE ( priority = ? OR priority > ? ) AND user = ?";
2147 @bind = ('2', '5', 'nwiger');
2149 If you want to include literal SQL (with or without bind values), just use a
2150 scalar reference or reference to an arrayref as the value:
2153 date_entered => { '>' => \["to_date(?, 'MM/DD/YYYY')", "11/26/2008"] },
2154 date_expires => { '<' => \"now()" }
2157 Which would generate:
2159 $stmt = "WHERE date_entered > to_date(?, 'MM/DD/YYYY') AND date_expires < now()";
2160 @bind = ('11/26/2008');
2163 =head2 Logic and nesting operators
2165 In the example above,
2166 there is a subtle trap if you want to say something like
2167 this (notice the C<AND>):
2169 WHERE priority != ? AND priority != ?
2171 Because, in Perl you I<can't> do this:
2173 priority => { '!=' => 2, '!=' => 1 }
2175 As the second C<!=> key will obliterate the first. The solution
2176 is to use the special C<-modifier> form inside an arrayref:
2178 priority => [ -and => {'!=', 2},
2182 Normally, these would be joined by C<OR>, but the modifier tells it
2183 to use C<AND> instead. (Hint: You can use this in conjunction with the
2184 C<logic> option to C<new()> in order to change the way your queries
2185 work by default.) B<Important:> Note that the C<-modifier> goes
2186 B<INSIDE> the arrayref, as an extra first element. This will
2187 B<NOT> do what you think it might:
2189 priority => -and => [{'!=', 2}, {'!=', 1}] # WRONG!
2191 Here is a quick list of equivalencies, since there is some overlap:
2194 status => {'!=', 'completed', 'not like', 'pending%' }
2195 status => [ -and => {'!=', 'completed'}, {'not like', 'pending%'}]
2198 status => {'=', ['assigned', 'in-progress']}
2199 status => [ -or => {'=', 'assigned'}, {'=', 'in-progress'}]
2200 status => [ {'=', 'assigned'}, {'=', 'in-progress'} ]
2204 =head2 Special operators: IN, BETWEEN, etc.
2206 You can also use the hashref format to compare a list of fields using the
2207 C<IN> comparison operator, by specifying the list as an arrayref:
2210 status => 'completed',
2211 reportid => { -in => [567, 2335, 2] }
2214 Which would generate:
2216 $stmt = "WHERE status = ? AND reportid IN (?,?,?)";
2217 @bind = ('completed', '567', '2335', '2');
2219 The reverse operator C<-not_in> generates SQL C<NOT IN> and is used in
2222 If the argument to C<-in> is an empty array, 'sqlfalse' is generated
2223 (by default: C<1=0>). Similarly, C<< -not_in => [] >> generates
2224 'sqltrue' (by default: C<1=1>).
2226 In addition to the array you can supply a chunk of literal sql or
2227 literal sql with bind:
2230 customer => { -in => \[
2231 'SELECT cust_id FROM cust WHERE balance > ?',
2234 status => { -in => \'SELECT status_codes FROM states' },
2240 customer IN ( SELECT cust_id FROM cust WHERE balance > ? )
2241 AND status IN ( SELECT status_codes FROM states )
2245 Finally, if the argument to C<-in> is not a reference, it will be
2246 treated as a single-element array.
2248 Another pair of operators is C<-between> and C<-not_between>,
2249 used with an arrayref of two values:
2253 completion_date => {
2254 -not_between => ['2002-10-01', '2003-02-06']
2260 WHERE user = ? AND completion_date NOT BETWEEN ( ? AND ? )
2262 Just like with C<-in> all plausible combinations of literal SQL
2266 start0 => { -between => [ 1, 2 ] },
2267 start1 => { -between => \["? AND ?", 1, 2] },
2268 start2 => { -between => \"lower(x) AND upper(y)" },
2269 start3 => { -between => [
2271 \["upper(?)", 'stuff' ],
2278 ( start0 BETWEEN ? AND ? )
2279 AND ( start1 BETWEEN ? AND ? )
2280 AND ( start2 BETWEEN lower(x) AND upper(y) )
2281 AND ( start3 BETWEEN lower(x) AND upper(?) )
2283 @bind = (1, 2, 1, 2, 'stuff');
2286 These are the two builtin "special operators"; but the
2287 list can be expanded: see section L</"SPECIAL OPERATORS"> below.
2289 =head2 Unary operators: bool
2291 If you wish to test against boolean columns or functions within your
2292 database you can use the C<-bool> and C<-not_bool> operators. For
2293 example to test the column C<is_user> being true and the column
2294 C<is_enabled> being false you would use:-
2298 -not_bool => 'is_enabled',
2303 WHERE is_user AND NOT is_enabled
2305 If a more complex combination is required, testing more conditions,
2306 then you should use the and/or operators:-
2311 -not_bool => { two=> { -rlike => 'bar' } },
2312 -not_bool => { three => [ { '=', 2 }, { '>', 5 } ] },
2323 (NOT ( three = ? OR three > ? ))
2326 =head2 Nested conditions, -and/-or prefixes
2328 So far, we've seen how multiple conditions are joined with a top-level
2329 C<AND>. We can change this by putting the different conditions we want in
2330 hashes and then putting those hashes in an array. For example:
2335 status => { -like => ['pending%', 'dispatched'] },
2339 status => 'unassigned',
2343 This data structure would create the following:
2345 $stmt = "WHERE ( user = ? AND ( status LIKE ? OR status LIKE ? ) )
2346 OR ( user = ? AND status = ? ) )";
2347 @bind = ('nwiger', 'pending', 'dispatched', 'robot', 'unassigned');
2350 Clauses in hashrefs or arrayrefs can be prefixed with an C<-and> or C<-or>
2351 to change the logic inside:
2357 -and => [ workhrs => {'>', 20}, geo => 'ASIA' ],
2358 -or => { workhrs => {'<', 50}, geo => 'EURO' },
2365 $stmt = "WHERE ( user = ?
2366 AND ( ( workhrs > ? AND geo = ? )
2367 OR ( workhrs < ? OR geo = ? ) ) )";
2368 @bind = ('nwiger', '20', 'ASIA', '50', 'EURO');
2370 =head3 Algebraic inconsistency, for historical reasons
2372 C<Important note>: when connecting several conditions, the C<-and->|C<-or>
2373 operator goes C<outside> of the nested structure; whereas when connecting
2374 several constraints on one column, the C<-and> operator goes
2375 C<inside> the arrayref. Here is an example combining both features:
2378 -and => [a => 1, b => 2],
2379 -or => [c => 3, d => 4],
2380 e => [-and => {-like => 'foo%'}, {-like => '%bar'} ]
2385 WHERE ( ( ( a = ? AND b = ? )
2386 OR ( c = ? OR d = ? )
2387 OR ( e LIKE ? AND e LIKE ? ) ) )
2389 This difference in syntax is unfortunate but must be preserved for
2390 historical reasons. So be careful: the two examples below would
2391 seem algebraically equivalent, but they are not
2394 { -like => 'foo%' },
2395 { -like => '%bar' },
2397 # yields: WHERE ( ( col LIKE ? AND col LIKE ? ) )
2400 { col => { -like => 'foo%' } },
2401 { col => { -like => '%bar' } },
2403 # yields: WHERE ( ( col LIKE ? OR col LIKE ? ) )
2406 =head2 Literal SQL and value type operators
2408 The basic premise of SQL::Abstract is that in WHERE specifications the "left
2409 side" is a column name and the "right side" is a value (normally rendered as
2410 a placeholder). This holds true for both hashrefs and arrayref pairs as you
2411 see in the L</WHERE CLAUSES> examples above. Sometimes it is necessary to
2412 alter this behavior. There are several ways of doing so.
2416 This is a virtual operator that signals the string to its right side is an
2417 identifier (a column name) and not a value. For example to compare two
2418 columns you would write:
2421 priority => { '<', 2 },
2422 requestor => { -ident => 'submitter' },
2427 $stmt = "WHERE priority < ? AND requestor = submitter";
2430 If you are maintaining legacy code you may see a different construct as
2431 described in L</Deprecated usage of Literal SQL>, please use C<-ident> in new
2436 This is a virtual operator that signals that the construct to its right side
2437 is a value to be passed to DBI. This is for example necessary when you want
2438 to write a where clause against an array (for RDBMS that support such
2439 datatypes). For example:
2442 array => { -value => [1, 2, 3] }
2447 $stmt = 'WHERE array = ?';
2448 @bind = ([1, 2, 3]);
2450 Note that if you were to simply say:
2456 the result would probably not be what you wanted:
2458 $stmt = 'WHERE array = ? OR array = ? OR array = ?';
2463 Finally, sometimes only literal SQL will do. To include a random snippet
2464 of SQL verbatim, you specify it as a scalar reference. Consider this only
2465 as a last resort. Usually there is a better way. For example:
2468 priority => { '<', 2 },
2469 requestor => { -in => \'(SELECT name FROM hitmen)' },
2474 $stmt = "WHERE priority < ? AND requestor IN (SELECT name FROM hitmen)"
2477 Note that in this example, you only get one bind parameter back, since
2478 the verbatim SQL is passed as part of the statement.
2482 Never use untrusted input as a literal SQL argument - this is a massive
2483 security risk (there is no way to check literal snippets for SQL
2484 injections and other nastyness). If you need to deal with untrusted input
2485 use literal SQL with placeholders as described next.
2487 =head3 Literal SQL with placeholders and bind values (subqueries)
2489 If the literal SQL to be inserted has placeholders and bind values,
2490 use a reference to an arrayref (yes this is a double reference --
2491 not so common, but perfectly legal Perl). For example, to find a date
2492 in Postgres you can use something like this:
2495 date_column => \[ "= date '2008-09-30' - ?::integer", 10 ]
2500 $stmt = "WHERE ( date_column = date '2008-09-30' - ?::integer )"
2503 Note that you must pass the bind values in the same format as they are returned
2504 by L<where|/where(\%where, $order)>. This means that if you set L</bindtype>
2505 to C<columns>, you must provide the bind values in the
2506 C<< [ column_meta => value ] >> format, where C<column_meta> is an opaque
2507 scalar value; most commonly the column name, but you can use any scalar value
2508 (including references and blessed references), L<SQL::Abstract> will simply
2509 pass it through intact. So if C<bindtype> is set to C<columns> the above
2510 example will look like:
2513 date_column => \[ "= date '2008-09-30' - ?::integer", [ {} => 10 ] ]
2516 Literal SQL is especially useful for nesting parenthesized clauses in the
2517 main SQL query. Here is a first example:
2519 my ($sub_stmt, @sub_bind) = ("SELECT c1 FROM t1 WHERE c2 < ? AND c3 LIKE ?",
2523 bar => \["IN ($sub_stmt)" => @sub_bind],
2528 $stmt = "WHERE (foo = ? AND bar IN (SELECT c1 FROM t1
2529 WHERE c2 < ? AND c3 LIKE ?))";
2530 @bind = (1234, 100, "foo%");
2532 Other subquery operators, like for example C<"E<gt> ALL"> or C<"NOT IN">,
2533 are expressed in the same way. Of course the C<$sub_stmt> and
2534 its associated bind values can be generated through a former call
2537 my ($sub_stmt, @sub_bind)
2538 = $sql->select("t1", "c1", {c2 => {"<" => 100},
2539 c3 => {-like => "foo%"}});
2542 bar => \["> ALL ($sub_stmt)" => @sub_bind],
2545 In the examples above, the subquery was used as an operator on a column;
2546 but the same principle also applies for a clause within the main C<%where>
2547 hash, like an EXISTS subquery:
2549 my ($sub_stmt, @sub_bind)
2550 = $sql->select("t1", "*", {c1 => 1, c2 => \"> t0.c0"});
2551 my %where = ( -and => [
2553 \["EXISTS ($sub_stmt)" => @sub_bind],
2558 $stmt = "WHERE (foo = ? AND EXISTS (SELECT * FROM t1
2559 WHERE c1 = ? AND c2 > t0.c0))";
2563 Observe that the condition on C<c2> in the subquery refers to
2564 column C<t0.c0> of the main query: this is I<not> a bind
2565 value, so we have to express it through a scalar ref.
2566 Writing C<< c2 => {">" => "t0.c0"} >> would have generated
2567 C<< c2 > ? >> with bind value C<"t0.c0"> ... not exactly
2568 what we wanted here.
2570 Finally, here is an example where a subquery is used
2571 for expressing unary negation:
2573 my ($sub_stmt, @sub_bind)
2574 = $sql->where({age => [{"<" => 10}, {">" => 20}]});
2575 $sub_stmt =~ s/^ where //i; # don't want "WHERE" in the subclause
2577 lname => {like => '%son%'},
2578 \["NOT ($sub_stmt)" => @sub_bind],
2583 $stmt = "lname LIKE ? AND NOT ( age < ? OR age > ? )"
2584 @bind = ('%son%', 10, 20)
2586 =head3 Deprecated usage of Literal SQL
2588 Below are some examples of archaic use of literal SQL. It is shown only as
2589 reference for those who deal with legacy code. Each example has a much
2590 better, cleaner and safer alternative that users should opt for in new code.
2596 my %where = ( requestor => \'IS NOT NULL' )
2598 $stmt = "WHERE requestor IS NOT NULL"
2600 This used to be the way of generating NULL comparisons, before the handling
2601 of C<undef> got formalized. For new code please use the superior syntax as
2602 described in L</Tests for NULL values>.
2606 my %where = ( requestor => \'= submitter' )
2608 $stmt = "WHERE requestor = submitter"
2610 This used to be the only way to compare columns. Use the superior L</-ident>
2611 method for all new code. For example an identifier declared in such a way
2612 will be properly quoted if L</quote_char> is properly set, while the legacy
2613 form will remain as supplied.
2617 my %where = ( is_ready => \"", completed => { '>', '2012-12-21' } )
2619 $stmt = "WHERE completed > ? AND is_ready"
2620 @bind = ('2012-12-21')
2622 Using an empty string literal used to be the only way to express a boolean.
2623 For all new code please use the much more readable
2624 L<-bool|/Unary operators: bool> operator.
2630 These pages could go on for a while, since the nesting of the data
2631 structures this module can handle are pretty much unlimited (the
2632 module implements the C<WHERE> expansion as a recursive function
2633 internally). Your best bet is to "play around" with the module a
2634 little to see how the data structures behave, and choose the best
2635 format for your data based on that.
2637 And of course, all the values above will probably be replaced with
2638 variables gotten from forms or the command line. After all, if you
2639 knew everything ahead of time, you wouldn't have to worry about
2640 dynamically-generating SQL and could just hardwire it into your
2643 =head1 ORDER BY CLAUSES
2645 Some functions take an order by clause. This can either be a scalar (just a
2646 column name), a hashref of C<< { -desc => 'col' } >> or C<< { -asc => 'col' }
2647 >>, a scalarref, an arrayref-ref, or an arrayref of any of the previous
2650 Given | Will Generate
2651 ---------------------------------------------------------------
2653 'colA' | ORDER BY colA
2655 [qw/colA colB/] | ORDER BY colA, colB
2657 {-asc => 'colA'} | ORDER BY colA ASC
2659 {-desc => 'colB'} | ORDER BY colB DESC
2661 ['colA', {-asc => 'colB'}] | ORDER BY colA, colB ASC
2663 { -asc => [qw/colA colB/] } | ORDER BY colA ASC, colB ASC
2665 \'colA DESC' | ORDER BY colA DESC
2667 \[ 'FUNC(colA, ?)', $x ] | ORDER BY FUNC(colA, ?)
2668 | /* ...with $x bound to ? */
2671 { -asc => 'colA' }, | colA ASC,
2672 { -desc => [qw/colB/] }, | colB DESC,
2673 { -asc => [qw/colC colD/] },| colC ASC, colD ASC,
2674 \'colE DESC', | colE DESC,
2675 \[ 'FUNC(colF, ?)', $x ], | FUNC(colF, ?)
2676 ] | /* ...with $x bound to ? */
2677 ===============================================================
2681 =head1 SPECIAL OPERATORS
2683 my $sqlmaker = SQL::Abstract->new(special_ops => [
2687 my ($self, $field, $op, $arg) = @_;
2693 handler => 'method_name',
2697 A "special operator" is a SQL syntactic clause that can be
2698 applied to a field, instead of a usual binary operator.
2701 WHERE field IN (?, ?, ?)
2702 WHERE field BETWEEN ? AND ?
2703 WHERE MATCH(field) AGAINST (?, ?)
2705 Special operators IN and BETWEEN are fairly standard and therefore
2706 are builtin within C<SQL::Abstract> (as the overridable methods
2707 C<_where_field_IN> and C<_where_field_BETWEEN>). For other operators,
2708 like the MATCH .. AGAINST example above which is specific to MySQL,
2709 you can write your own operator handlers - supply a C<special_ops>
2710 argument to the C<new> method. That argument takes an arrayref of
2711 operator definitions; each operator definition is a hashref with two
2718 the regular expression to match the operator
2722 Either a coderef or a plain scalar method name. In both cases
2723 the expected return is C<< ($sql, @bind) >>.
2725 When supplied with a method name, it is simply called on the
2726 L<SQL::Abstract> object as:
2728 $self->$method_name($field, $op, $arg)
2732 $field is the LHS of the operator
2733 $op is the part that matched the handler regex
2736 When supplied with a coderef, it is called as:
2738 $coderef->($self, $field, $op, $arg)
2743 For example, here is an implementation
2744 of the MATCH .. AGAINST syntax for MySQL
2746 my $sqlmaker = SQL::Abstract->new(special_ops => [
2748 # special op for MySql MATCH (field) AGAINST(word1, word2, ...)
2749 {regex => qr/^match$/i,
2751 my ($self, $field, $op, $arg) = @_;
2752 $arg = [$arg] if not ref $arg;
2753 my $label = $self->_quote($field);
2754 my ($placeholder) = $self->_convert('?');
2755 my $placeholders = join ", ", (($placeholder) x @$arg);
2756 my $sql = $self->_sqlcase('match') . " ($label) "
2757 . $self->_sqlcase('against') . " ($placeholders) ";
2758 my @bind = $self->_bindtype($field, @$arg);
2759 return ($sql, @bind);
2766 =head1 UNARY OPERATORS
2768 my $sqlmaker = SQL::Abstract->new(unary_ops => [
2772 my ($self, $op, $arg) = @_;
2778 handler => 'method_name',
2782 A "unary operator" is a SQL syntactic clause that can be
2783 applied to a field - the operator goes before the field
2785 You can write your own operator handlers - supply a C<unary_ops>
2786 argument to the C<new> method. That argument takes an arrayref of
2787 operator definitions; each operator definition is a hashref with two
2794 the regular expression to match the operator
2798 Either a coderef or a plain scalar method name. In both cases
2799 the expected return is C<< $sql >>.
2801 When supplied with a method name, it is simply called on the
2802 L<SQL::Abstract> object as:
2804 $self->$method_name($op, $arg)
2808 $op is the part that matched the handler regex
2809 $arg is the RHS or argument of the operator
2811 When supplied with a coderef, it is called as:
2813 $coderef->($self, $op, $arg)
2821 Thanks to some benchmarking by Mark Stosberg, it turns out that
2822 this module is many orders of magnitude faster than using C<DBIx::Abstract>.
2823 I must admit this wasn't an intentional design issue, but it's a
2824 byproduct of the fact that you get to control your C<DBI> handles
2827 To maximize performance, use a code snippet like the following:
2829 # prepare a statement handle using the first row
2830 # and then reuse it for the rest of the rows
2832 for my $href (@array_of_hashrefs) {
2833 $stmt ||= $sql->insert('table', $href);
2834 $sth ||= $dbh->prepare($stmt);
2835 $sth->execute($sql->values($href));
2838 The reason this works is because the keys in your C<$href> are sorted
2839 internally by B<SQL::Abstract>. Thus, as long as your data retains
2840 the same structure, you only have to generate the SQL the first time
2841 around. On subsequent queries, simply use the C<values> function provided
2842 by this module to return your values in the correct order.
2844 However this depends on the values having the same type - if, for
2845 example, the values of a where clause may either have values
2846 (resulting in sql of the form C<column = ?> with a single bind
2847 value), or alternatively the values might be C<undef> (resulting in
2848 sql of the form C<column IS NULL> with no bind value) then the
2849 caching technique suggested will not work.
2853 If you use my C<CGI::FormBuilder> module at all, you'll hopefully
2854 really like this part (I do, at least). Building up a complex query
2855 can be as simple as the following:
2862 use CGI::FormBuilder;
2865 my $form = CGI::FormBuilder->new(...);
2866 my $sql = SQL::Abstract->new;
2868 if ($form->submitted) {
2869 my $field = $form->field;
2870 my $id = delete $field->{id};
2871 my($stmt, @bind) = $sql->update('table', $field, {id => $id});
2874 Of course, you would still have to connect using C<DBI> to run the
2875 query, but the point is that if you make your form look like your
2876 table, the actual query script can be extremely simplistic.
2878 If you're B<REALLY> lazy (I am), check out C<HTML::QuickTable> for
2879 a fast interface to returning and formatting data. I frequently
2880 use these three modules together to write complex database query
2881 apps in under 50 lines.
2883 =head1 HOW TO CONTRIBUTE
2885 Contributions are always welcome, in all usable forms (we especially
2886 welcome documentation improvements). The delivery methods include git-
2887 or unified-diff formatted patches, GitHub pull requests, or plain bug
2888 reports either via RT or the Mailing list. Contributors are generally
2889 granted full access to the official repository after their first several
2890 patches pass successful review.
2892 This project is maintained in a git repository. The code and related tools are
2893 accessible at the following locations:
2897 =item * Official repo: L<git://git.shadowcat.co.uk/dbsrgits/SQL-Abstract.git>
2899 =item * Official gitweb: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits/SQL-Abstract.git>
2901 =item * GitHub mirror: L<https://github.com/dbsrgits/sql-abstract>
2903 =item * Authorized committers: L<ssh://dbsrgits@git.shadowcat.co.uk/SQL-Abstract.git>
2909 Version 1.50 was a major internal refactoring of C<SQL::Abstract>.
2910 Great care has been taken to preserve the I<published> behavior
2911 documented in previous versions in the 1.* family; however,
2912 some features that were previously undocumented, or behaved
2913 differently from the documentation, had to be changed in order
2914 to clarify the semantics. Hence, client code that was relying
2915 on some dark areas of C<SQL::Abstract> v1.*
2916 B<might behave differently> in v1.50.
2918 The main changes are:
2924 support for literal SQL through the C<< \ [ $sql, @bind ] >> syntax.
2928 support for the { operator => \"..." } construct (to embed literal SQL)
2932 support for the { operator => \["...", @bind] } construct (to embed literal SQL with bind values)
2936 optional support for L<array datatypes|/"Inserting and Updating Arrays">
2940 defensive programming: check arguments
2944 fixed bug with global logic, which was previously implemented
2945 through global variables yielding side-effects. Prior versions would
2946 interpret C<< [ {cond1, cond2}, [cond3, cond4] ] >>
2947 as C<< "(cond1 AND cond2) OR (cond3 AND cond4)" >>.
2948 Now this is interpreted
2949 as C<< "(cond1 AND cond2) OR (cond3 OR cond4)" >>.
2954 fixed semantics of _bindtype on array args
2958 dropped the C<_anoncopy> of the %where tree. No longer necessary,
2959 we just avoid shifting arrays within that tree.
2963 dropped the C<_modlogic> function
2967 =head1 ACKNOWLEDGEMENTS
2969 There are a number of individuals that have really helped out with
2970 this module. Unfortunately, most of them submitted bugs via CPAN
2971 so I have no idea who they are! But the people I do know are:
2973 Ash Berlin (order_by hash term support)
2974 Matt Trout (DBIx::Class support)
2975 Mark Stosberg (benchmarking)
2976 Chas Owens (initial "IN" operator support)
2977 Philip Collins (per-field SQL functions)
2978 Eric Kolve (hashref "AND" support)
2979 Mike Fragassi (enhancements to "BETWEEN" and "LIKE")
2980 Dan Kubb (support for "quote_char" and "name_sep")
2981 Guillermo Roditi (patch to cleanup "IN" and "BETWEEN", fix and tests for _order_by)
2982 Laurent Dami (internal refactoring, extensible list of special operators, literal SQL)
2983 Norbert Buchmuller (support for literal SQL in hashpair, misc. fixes & tests)
2984 Peter Rabbitson (rewrite of SQLA::Test, misc. fixes & tests)
2985 Oliver Charles (support for "RETURNING" after "INSERT")
2991 L<DBIx::Class>, L<DBIx::Abstract>, L<CGI::FormBuilder>, L<HTML::QuickTable>.
2995 Copyright (c) 2001-2007 Nathan Wiger <nwiger@cpan.org>. All Rights Reserved.
2997 This module is actively maintained by Matt Trout <mst@shadowcatsystems.co.uk>
2999 For support, your best bet is to try the C<DBIx::Class> users mailing list.
3000 While not an official support venue, C<DBIx::Class> makes heavy use of
3001 C<SQL::Abstract>, and as such list members there are very familiar with
3002 how to create queries.
3006 This module is free software; you may copy this under the same
3007 terms as perl itself (either the GNU General Public License or
3008 the Artistic License)