package SQL::Interpolate::Macro; use strict; use warnings; use base qw(Exporter); use SQL::Interpolate; BEGIN { SQL::Interpolate::_enable_macros(); } our $VERSION = '0.33'; our @EXPORT; our %EXPORT_TAGS = (all => [qw( sql_and sql_flatten sql_if sql_link sql_or sql_paren sql_rel sql_rel_filter relations sql_fragment )]); # note: relations and sql_fragment depreciated our @EXPORT_OK = @{$EXPORT_TAGS{'all'}}; sub sql_flatten; sub sql_flatten { my (@items) = @_; # extract optional state parameter my $state; my $interp; if (ref $items[0] eq 'DBI::db') { $state = shift @items; } elsif (UNIVERSAL::isa($items[0], 'SQL::Interpolate')) { $state = $interp = shift @items; } # flatten items @items = map { my $e = $_; if (UNIVERSAL::isa($e, 'SQL::Interpolate::Macro')) { my @out = $e->expand($state); sql_flatten $state || (), @out; } elsif (ref $e eq 'SQL::Interpolate::SQL') { sql_flatten $state || (), @$e; } elsif (ref $e eq 'ARRAY') { # detect if array might contain macros # and such that might need flattening my $is_complex = 0; IS_COMPLEX: for my $e2 (@$e) { my $ref2 = ref $e2; if ($ref2 eq 'ARRAY') { for my $e3 (@$e2) { if (ref $e3 ne '') { $is_complex = 1; last IS_COMPLEX; } } } elsif ($ref2 eq 'HASH') { for my $e3 (values %$e2) { if (ref $e3 ne '') { $is_complex = 1; last IS_COMPLEX; } } } elsif ($ref2 ne '') { $is_complex = 1; last IS_COMPLEX; } } if ($is_complex) { my @array_out = @$e; for my $o_out (@array_out) { $o_out = _flatten_single($state, $o_out); } \@array_out; } else { $e; } } elsif (ref $e eq 'HASH') { # detect if hash might contain macros # and such that might need flattening my $is_complex = 0; IS_COMPLEX: for my $e2 (values %$e) { my $ref2 = ref $e2; if ($ref2 ne '') { $is_complex = 1; last IS_COMPLEX; } } if ($is_complex) { my %hash_out = %$e; for my $o_out (values %hash_out) { $o_out = _flatten_single($state, $o_out); } \%hash_out; } else { $e; } } elsif (ref $e eq '') { # SQL string # apply any filters to string and expand any new macros if ($interp && @{$interp->{text_fragment_filters}} != 0) { my @out = ($e); for my $filter (@{$interp->{text_fragment_filters}}) { @out = $filter->filter_text_fragment($e); my $same = @out == 1 && ref $out[0] eq '' && $out[0] eq $e; unless($same) { @out = sql_flatten($state || (), @out); last; } } @out } else { $e } } else { $e } } @items; return @items; } # flattens an element that expands to a single # element (e.g. an element in an array) sub _flatten_single { my($state, $o) = @_; my $o_out; # first flatten element if macro if (UNIVERSAL::isa($o, 'SQL::Interpolate::Macro')) { my @items = $o->expand($state); # improve--what if macros are returned? if(@items == 1) { $o_out = $items[0]; } else { $o_out = SQL::Interpolate::SQL->new(@items); } } else { $o_out = $o; } if (ref $o_out eq 'SQL::Interpolate::SQL') { $o_out = SQL::Interpolate::SQL->new(sql_flatten $state || (), @$o_out); } elsif (ref $o_out eq '' or ref $o_out eq 'SQL::Interpolate::Variable') { # nothing } elsif (ref $o_out eq 'ARRAY') { my @row_out = @$o_out; for my $o2_out (@row_out) { $o2_out = _flatten_single($state, $o2_out); } $o_out = \@row_out; } elsif (ref $o_out eq 'HASH') { my %row_out = %$o_out; for my $o2_out (values %row_out) { $o2_out = _flatten_single($state, $o2_out); } $o_out = \%row_out; } else { die "FIX:$o_out"; # unrecognized } return $o_out; } sub sql_and { return SQL::Interpolate::And->new(@_); } sub sql_or { return SQL::Interpolate::Or->new(@_); } sub sql_if { return SQL::Interpolate::If->new(@_); } sub sql_rel { return SQL::Interpolate::Rel->new(@_); } sub sql_link { return SQL::Interpolate::Link->new(@_); } sub sql_paren { return SQL::Interpolate::Paren->new(@_); } sub sql_rel_filter { return SQL::Interpolate::RelProcessor->new(@_); } # depreciated sub relations { print STDERR "SQL::Interpolate::Macro - WARNING: " . "relations() is depreciated. use sql_rel_filter() instead.\n"; return sql_rel_filter(@_); } # [private] # Given instances of two relations, generate the SQL to link them. # For example, # ['Sp', ['S', 'p'], $sales_ord_line] and # ['p', ['p'], $part] # gives "Sp.part_nbr = p.part_nbr". # params: # $e1 - entity 1 # $e2 - entity 2 # where each instance is a arrayref of an entity relation name, a arrayref of # names of contained entities, and a relation # specification (as passed into C). sub _single_link_sql { my ($e1, $e2) = @_; my ($left_idx, $right_idx); if ($e1->[1]->[0] eq $e2->[1]->[0]) { $left_idx=0; $right_idx=0; } elsif (defined($e2->[1]->[1]) && $e1->[1]->[0] eq $e2->[1]->[1]) { $left_idx=0; $right_idx=1; } elsif (defined($e1->[1]->[1]) && $e1->[1]->[1] eq $e2->[1]->[0]) { $left_idx=1; $right_idx=0; } elsif (defined($e1->[1]->[1]) && defined($e2->[1]->[1]) && $e1->[1]->[1] eq $e2->[1]->[1]) { $left_idx=1; $right_idx=1; } else { die "Invalid SQL link [$e1->[0] to $e2->[0]]"; } my $sql = "$e1->[0].$e1->[2]->{key}->[$left_idx ]" . " = " . "$e2->[0].$e2->[2]->{key}->[$right_idx]"; return $sql; } # depreciated sub sql_fragment { print STDERR "SQL::Interpolate::Macro - WARNING: " . "sql_fragment() is depreciated. use sql() instead.\n"; return SQL::Interpolate::SQL->new(@_); } 1; package SQL::Interpolate::SQLFilter; use strict; use warnings; #IMPROVE: package name? 1; package SQL::Interpolate::RelProcessor; use base 'SQL::Interpolate::SQLFilter'; use strict; use warnings; sub new { my ($class, $relations) = @_; return bless { relations => $relations, keys => {} }, $class; } sub init { my $self = shift; $self->{keys} = {}; return; } sub filter_text { my ($self, $sql) = @_; while (my ($name, $key) = each %{$self->{keys}}) { $sql =~ s{ (?new($1); } elsif ($sql =~ m{\G \b LINK \( (.*?) \)}xsgc) { push @out, substr($sql, $pos0, $pos1 - $pos0) if $pos1 != $pos0; $pos0 = pos($sql); my $params = $1; my @params = split /,/, $params; s{^\s*|\s*$}{}gs for @params; push @out, SQL::Interpolate::Link->new(@params); } else { $sql =~ m{\G.[^RL]*}xsgc; } } my $pos1 = pos($sql); push @out, substr($sql, $pos0, $pos1 - $pos0) if $pos1 != $pos0; return @out; } 1; package SQL::Interpolate::Rel; use strict; use base 'SQL::Interpolate::Macro'; sub new { my ($class, $name) = @_; my $self = bless [ $name ], $class; return $self; } sub expand { my ($self, $interp) = @_; # improve-method call? my $filters = $interp->{filters_hash}->{'SQL::Interpolate::RelProcessor'}; die "No sql_rel_filter defined" if ! defined $filters; die "Multiple relation filters currently not supported" if @$filters > 1; my $filter = $filters->[0]; my $keys = $filter->{keys}; my $name = $self->[0]; my $sql; for my $relation_name (keys %{$filter->{relations}}) { my $relation = $filter->{relations}->{$relation_name}; my $name_re = $relation->{name}; if ($name =~ /($name_re)/s) { my ($name, $name1, $name2) = ($1, $2, $3); $keys->{$name1} = "$name.$relation->{key}->[0]"; $keys->{$name2} = "$name.$relation->{key}->[1]" if defined $relation->{key}->[1]; $sql = "$relation_name as $name"; last; } } if (! defined $sql) { die "Unrecognized relation REL($name)."; } return $sql; } 1; package SQL::Interpolate::Link; use strict; use base 'SQL::Interpolate::Macro'; sub new { my ($class, @rels) = @_; my $self = bless [ @rels ], $class; return $self; } sub expand { my ($self, $interp) = @_; # improve-method call? my $filters = $interp->{filters_hash}->{'SQL::Interpolate::RelProcessor'}; die "No sql_rel_filter filter defined" if ! defined $filters; die "Multiple relation filters currently not supported" if @$filters > 1; my $filter = $filters->[0]; my @params = @$self; my $good = 1; my $last; for my $param (@params) { my $match = 0; done_param: for my $relation (values %{$filter->{relations}}) { my $name_re = $relation->{name}; if ($param =~ /($name_re)/gs) { my ($name, $name1, $name2) = ($1, $2, $3); $param = [$name, [$name1, defined($name2) ? $name2 : ()], $relation]; $match = 1; last done_param; } } if (!$match) { die "Invalid param [$param] in LINK macro in SQL template."; } } # relations touching entities. my %links; my @sql_snips; for my $param (@params) { for my $entity (@{$param->[1]}) { if (defined $links{$entity}) { push @sql_snips, SQL::Interpolate::Macro::_single_link_sql( $links{$entity}, $param); } } $links{$param->[1]->[0]} = $param; $links{$param->[1]->[1]} = $param if defined $param->[1]->[1]; } my $sql = join ' AND ', @sql_snips; $sql = "($sql)" if @sql_snips > 1; return $sql; } 1; package SQL::Interpolate::Paren; use strict; use base 'SQL::Interpolate::Macro'; sub new { my ($class, @elements) = @_; my $self = bless [ @elements ], $class; return $self; } sub expand { my ($self, $interp) = @_; return ('(', SQL::Interpolate::Macro::sql_flatten( $interp || (), @$self), ')'); } 1; package SQL::Interpolate::And; use strict; use base 'SQL::Interpolate::Macro'; sub new { my ($class, @elements) = @_; my $self = bless [@elements], $class; return $self; } sub expand { my ($self, $interp) = @_; my @out = map { my @expand = SQL::Interpolate::Macro::sql_flatten $interp || (), $_; (@expand == 0) ? () : ('AND', '(', @expand, ')') } @$self; shift @out; return '1=1' if @out == 0; # trivial case @out = ('(', @out, ')') if @out != 0; return @out; } 1; package SQL::Interpolate::Or; use strict; use base 'SQL::Interpolate::Macro'; sub new { my ($class, @elements) = @_; my $self = bless [ @elements ], $class; return $self; } sub expand { my ($self, $interp) = @_; my @out = map { my @expand = SQL::Interpolate::Macro::sql_flatten $interp || (), $_; (@expand == 0) ? () : ('OR', '(', @expand, ')') } @$self; shift @out; return '1=0' if @out == 0; # trivial case @out = ('(', @out, ')') if @out != 0; return @out; } 1; package SQL::Interpolate::If; use strict; use base 'SQL::Interpolate::Macro'; sub new { my ($class, $condition, $value_if_true) = @_; my $self = bless [ $condition, $value_if_true ], $class; return $self; } sub expand { my ($self, $interp) = @_; return $self->[0] ? SQL::Interpolate::Macro::sql_flatten($interp || (), $self->[1]) : (); } 1; __END__ =head1 NAME SQL::Interpolate::Macro - Macros and filters for SQL::Interpolate =head1 SYNOPSIS use SQL::Interpolate qw(:all); use SQL::Interpolate::Macro qw(:all); # Query that uses macros that assist in SQL building: sql_interp 'SELECT * FROM mytable WHERE', sql_and( sql_if($blue, q( color = "blue" )), sql_if($shape, sql('shape =', \$shape)) ), 'LIMIT 10'; # Macros and filters can perform automatic table joining. # First specify database layout: my $interp = SQL::Interpolate->new(sql_rel_filter( sales_order => {name => qr/([S-T])/, key => ['so_nbr']}, part => {name => qr/([p-r])/, key => ['part_nbr']}, sales_order_line => {name => qr/([S-T])([p-r])/, key => ['so_nbr', 'part_nbr']} ))->make_sql_interp(); # Then do queries: ($sql, @bind) = $interp->(' SELECT * FROM REL(S), REL(Sp), REL(p) WHERE LINK(S,Sp,p) AND S = 123 '); # RESULT: # $sql = 'SELECT * # FROM sales_order as S, sales_order_line as Sp, part as p # WHERE S.so_nbr = Sp.so_nbr AND Sp.part_nbr = p.part_nbr AND # S.so_nbr = 123' =head1 DESCRIPTION This module provides macro and filter capabilities to further simplify the construction of SQL queries using L and L (please read the documentation on those two modules for background). Various macros and filters are included as well as a framework for writing your own. Macros are objects that expand into an ordinary interpolation list via the C function: my @items = sql_flatten sql_and('X=Y', sql('Z=', 2)) # RESULT: @items = '(', 'X=Y', 'AND', 'Z=', \2, ')' Macros are derived from SQL::Interpolate::Macro. Macros may also exist as a convenience as "stringified macros," which are strings that filters may expand into real macro objects: $interp->sql_flatten('WHERE LINK(AB,BC) AND x=y') $interp->sql_flatten('WHERE', link('AB','BC'), 'AND x=y') # equivalent Also, source filtering, if enabled, internally converts sql// quotes into macro objects as well. An I is an object used to by C to assist in macro expansion and/or filtering of SQL text. The filtering on SQL text can occur before and/or after the SQL fragments are interpolated into a single string. my $interp = SQL::Interplate->new( funny_english_filter() ); $interp->sql_flatten('WHERE the value is', \2) OUTPUT: ('WHERE x =', \2) Filter objects are derived from SQL::Interpolate::SQLFilter. C is not normally called directly but rather is internally by C iff macros are enabled. The process can be recursive since the expansion of a macro may contain other (e.g. nested) macros. =head2 Motivation One use of this module is to handle trivial cases uniformly. For example, my @conditions = ...; # list of SQL conditional statements. sql_interp "x=2 OR", sql_and(@conditions); If @conditions > 0, this expands to sql_interp 'x=2 OR', '(', $conditions[0], 'AND', $conditions[1], 'AND', ...., ')'; If @conditions == 0, this expands to sql_interp "x=2 AND", "1=1"; # equivalent to "x=2" since sql_and() returns "1=1" # analogous to x^0 = 1 sql_or() returns "1=0" # analogous to x*0 = 0 Also, though a minor point, say you didn't match the parenthesis correctly in your interpolation list: "WHERE thid IN", \@thids, "AND ( action IN", \@admin_aids, "OR action IN", ['post', 'reply', 'edit'] This error would be caught at runtime, but it would be caught (earlier) at compile time if written as such: "WHERE thid IN", \@thids, "AND", sql("action IN", \@admin_aids, "OR action IN", ['post', 'reply', 'edit'] # -- syntax error by compiler =head2 Built-in Macros and Filters This module comes with various macros and SQL filters already implemented. See the sections below. =head2 Writing your own macros Here is a trivial example of writing your own macro-like function without using this framework at all. sub myparen { return '(', @_, ')'; } Example usage: my ($sql, @bind) = sql_interp "WHERE", my_paren("x=", \$x); # RESULT: # $sql = "WHERE (x=?)"; # @bind = $x; This simple expansion is not always sufficient though. In the following cases, macro expansion should not occur at the time Perl calls the macro function but rather later during the execution of C. (1) if the macro expansion needs data that is available only to an instance of SQL::Interpolate (e.g. a database handle that is interrogated to generate database-dependent SQL) or (2) to support recursive macros properly, e.g. sql_interp sql_and(sql_or('x=y', 'y=z'), 'z=w') # Don't expand to # sql_interp sql_and('(', 'x=y', 'y=z', ')', 'z=w') # and then to # sql_interp '(', 'AND', 'x=y', 'AND', 'y=z', 'AND', ')', 'AND', 'z=w' # but rahter expand to # sql_interp '(', sql_or('x=y', 'y=z'), 'AND', 'z=w', ')' # and then to # sql_interp '(', '(', 'x=y', 'OR', 'y=z', ')', 'AND', 'z=w', ')' Notice how the expansion in the last example must be done outside-to-in rather inside-to-out. A macro may be defined as follows. # helper function for simpler syntax sub myparen { return MyParen->new(@_); } # Macro class package MyParen; use base 'SQL::Interpolate::Macro'; sub new { my ($class, @elements) = @_; my $self = bless [ @elements ], $class; return $self; } sub expand { my ($self, $interp) = @_; my $dbh = $interp->{dbh}; if (defined($dbh) && $dbh->{Driver}->{Name} eq 'funnydatabase') { return ('leftparen', @$self, 'rightparen'); } else { return ('(', @$self, ')'); } } 1; Here, C returns a macro object, which can be placed onto an interpolation list. During the flattening phase, C calls C which calls the C method on the macro object, and this method must return the interpolation list that the macro will expand to. If the interpolation list macro contains macros itself, an sql_interp will further expand these. See also the source code of the macros provided in this module for more complex examples. =head2 Writing your own SQL filters The following is an example that expands on the previous example but supports a stringified version of the macro in the SQL literals. # example usage: my $interp = SQL::Interpolate->new(myparen_filter())->make_closure(); ($sql, @bind) = $interp->("SELECT * FROM mytable WHERE MYPAREN(x=y)"); # Equivalent to: # sql_interp "SELECT * FROM mytable WHERE ", # helper function for simpler syntax sub myparen_filter { return MyParenFilter->new(@_); } # SQL Filter class package MyParenFilter; use base 'SQL::Interpolate::SQLFilter'; # Filter a single SQL string fragment (during expansion) sub filter_text_fragment { my ($self, $sql) = @_; my @items; pos($sql) = 0; my $pos0 = pos($sql); until ($sql =~ /\G$/gc) { my $pos1 = pos($sql); if ($sql =~ m{\G \b MYPAREN \( (.*?) \)}xsgc) { push @items, substr($sql, $pos0, $pos1 - $pos0) if $pos1 != $pos0; $pos0 = pos($sql); push @items, MyParen->new($1); } else { $sql =~ m{\G.}xsgc; # more efficiently: \G.[^P]* } } my $pos1 = pos($sql); push @items, substr($sql, $pos0, $pos1 - $pos0) if $pos1 != $pos0; return @items; } 1; Your SQL filter may optionally have a few other methods that will be called by sql_interp if they exist. See L for details. =head1 INTERFACE =head2 Main functions =over 4 =item C @list_out = sql_flatten(@list_in); # functional @list_out = $interp->sql_flatten(@list_in); # OO Fully expands all macros in an interpolation list such that only strings, variables references, and sql() contains are left (no macros). Any macros in inside variable references are expanded to the other types of elements. my @list = sql_flatten sql/SELECT * FROM mytable where x=$x/; # OUTPUT: @list = ('SELECT * FROM mytable where x=', \$x); This function takes the same type of input as C, and, in fact, C uses it to preprocess input. This function is called internally by C if you use SQL::Interpolate::Macro. Therefore you would rarely need to call it directly. =back =head2 Builtin Filters =over 4 =item C The filter can simplify table joins by aliasing your tables and keys using special naming conventions and by writing the SQL expressions that link tables together via keys. It can be particularly useful to represent recursive data structures in a relational database, where the table join requirements are complicated. This allows one to write my $dbx = DBIx::Interpolate->new(sql_rel_filter( sales_order => {name => qr/^([S-T])$/, key => ['so_nbr']}, part => {name => qr/^([p-r])$/, key => ['part_nbr']}, sales_order_line => {name => qr/^([S-T])([p-r])$/, key => ['so_nbr', 'part_nbr']} )); $dbx->selectall_arrayref(' SELECT * FROM REL(S), REL(Sp), REL(p) WHERE LINK(S,Sp,p) AND S = 123 '); instead of $dbh->selectall_arrayref(' SELECT * FROM sales_order as S, sales_order_line as Sp, part as p WHERE S.so_nbr = Sp.so_nbr AND Sp.part_nbr = p.part_nbr AND S.so_nbr = 123 '); or $dbh->selectall_arrayref(' SELECT * FROM sales_order as S JOIN sales_order_line as Sp USING (so_nbr) JOIN part as p USING (part_nbr) '); The above example prints part information for all the line items on sales order #123. The table naming convention is that the names resemble the entities related by the tables, and this is a natural way to write queries. In the above example the entities are sales order (S) and part (p), which are related by the table represented by the juxtaposition "Sp". The LINK(S,Sp,p) macro expands by equating the keys in the given relations that identity the same entities according to the naming convention: "S" and "Sp" share S --> "S.so_nbr = Sp.so_nbr" "Sp" and "p" share p --> "Sp.part_nbr = p.part_nbr" Also, any entity written alone in an expression (e.g. "S" in "S = 123" above) is considered to be shorthand for primary key in a relation representing that entity: "S = 123" --> "S.so_nbr = 123" The C function above describes how the naming conventions map to your database schema. The meaning in this example is as follows. sales order entities can be represented by the names "S" and "T". Part entities can be represented by the names "p", "q", and "r". The juxtaposition of one of each entity name represents a row in the sales_order_line relation that relates these two entities. The entity names in the matches must be surrounded by capturing parenthesis (). The names in the key list correspond respectively to the entities captured in the match, and these names are the names of the primary or foreign keys (in the current relation) that identify the entities. For example, "Sp" represents a row in the sales_order_line table, with represents a relationship between a sales order entity (S) and part entity (p). The key for S is given by Sp.so_nbr, and the key for p is given by Sp.part_nbr. Also, consider a product structure that is represented in the database where parts can contain (subcomponent) parts that can in turn contain other (subcomponent) parts: sql_rel_filter(... part_part => { name => qr/^([p-r])([p-r])$/, key => ['part_nbr1', 'part_nbr2']} ) Now, it is possible to use two entities in the same class in the same relation: SELECT * FROM REL(pq), REL(qs) WHERE LINK(pq,qs) Table linking is not limited to SELECT statements either: UPDATE REL(Sp), REL(p) SET p.color = 'blue' WHERE LINK(Sp,p) AND S = $sonbr The SQL may contain these macros: REL(...) - identify relation and entities on it. This is converted into an SQL::Interpolate::Rel object. LINK(X,Y,Z,...) forms a Boolean expression linking the provided relations. There must be at least one parameter (typically two). This is converted into an SQL::Interpolate::Link object. $sql_in : string - input string $sql_out : string - output string The utility of automatic table linking is probably best shown by a real-world example. See Meset::MessageBoard in the L section, which use recursive data structures: sql_rel_filter({ messageset => {name => qr/^[A-Z]$/, key => 'msid'}, message => {name => qr/^[m-p]$/, key => 'mid'}, messageset_message => {foreign => { msid => 'messageset', mid => 'message' }}, messageset_messageset => {foreign => { msid_1 => 'messageset', msid_2 => 'messageset' }}, }); This expands simplified SQL such as SELECT * FROM REL(Am), REL(m) WHERE A = ? AND LINK(Am, m) into standard SQL: SELECT * FROM messageset_message as Am, message as m WHERE Am.msid = ? AND Am.mid = m.mid =back =head2 Builtin Macros =over 4 =item C $macro = sql_and(@predicates); Creates a macro object (SQL::Interpolate::And) representing a Boolean AND over a list of predicates. ($sql, @bind) = sql_interp sql_and( 'x=y', 'y=z or z=w', sql('z=', \3)) Generates ('((x=y) AND (y=z or z=w) AND (z=?))', 3) If the @predicates list is empty, a '1=1' is returned. ($sql, @bind) = sql_interp 'x=y AND', sql_and(@predicates); # Result: $sql = 'x=y AND 1=1'; Predicates are surrounded by parenthesis if possibly needed. =item C $macro = sql_or(@predicates); Creates a macro object (SQL::Interpolate::Or) representing a Boolean OR over a list of predicates. ($sql, @bind) = sql_interp sql_or('x=y', 'y=z', sql_paren('z=', \3)) Generates ('(x=y OR y=z OR 'z=?)', 3) If the @predicates list is empty, a '1=0' is returned. ($sql, @bind) = sql_interp 'x=y OR', sql_or(@predicates); # Generates $sql = 'x=y OR 1=0'; Predicates are surrounded by parenthesis if possibly needed. =item C $macro = sql_paren(@objs) Creates a macro object (SQL::Interpolate::Paren) representing a list of interpolation objects to be surrounded by parenthesis. ($sql, @bind) = sql_interp sql_paren('x=y AND z=', \3) # Generates ($sql, @bind) = ('(x=y and z=?)', 3); Typically, the size of the interpolation list should not be zero. =item C $macro = sql_if($condition, $value_if_true) Creates a macro object (SQL::Interpolate::If) that expands to the given value if the condition is true, else if expands to the empty list (). ($sql, @bind) = sql_interp sql_and( sql_if($blue, q(color = "blue")), sql_if($shape, sql_paren('shape =', \$shape)) ) # Generates one of # q((color = "blue" AND shape = ?)), $shape # q((color = "blue")) # q((shape = ?)), $shape # 1=1, $shape sql_if is similar to $condition ? $value_if_true : () except that it is a macro and therefore is evaluated at the time that C is processed. =item C $macro = sql_rel($alias) Creates a macro object (SQL::Interpolate::Rel) that expands to a table and alias definition based on the database description given in C. See C above for details. =item C $macro = sql_link(@aliases) Creates a macro object (SQL::Interpolate::Link) that expands to a table join condition definition based on the database description given in C. See the C above for details. =back =head2 SQL::Interpolate::SQL::Filter Methods The following methods are implemented by SQL filter objects (i.e. objects derived from SQL::Interpolate::SQLFilter). Many of these methods are called by C during interpolation, and many of these methods are optional. =over 4 =item C Initializes (or reinitializes) the macro object. This is called by C each time C begins processing to reset any state. This method is optional. sub init { my ($self) = @_; ... reinitialize self } =item C Filter a single SQL string fragment. This is called by C during expansion. This method is optional. sub filter_text_fragment { my ($self, $sql) = @_; if ($sql =~ /.../) { # match ... expand and return new list of interpolation entities return (...); } else { return $sql; # return original string (unmodified) } } One use of filter_text_fragment is to expand any macros embedded inside strings. "SELECT REL(AB), REL(BC) ..." expands to "SELECT ", rel('AB'), ', ', rel('BC'), ' ...' =item C Filter SQL string. This is called by C after macro expansion. This method is optional. sub filter_text { my ($self, $sql) = @_; ...transform $sql... return $sql; } Compare this to C, which is processed earlier. =back =head2 SQL::Interpolate::Macro Methods The following methods are implemented by macro objects (i.e. objects derived from SQL::Interpolate::Macro). =over 4 =item C Expands macro to an expanded interpolation list. This is called by C during macro expansion. sub expand { my ($self, $interp) = @_; ...expand self to interpolation list @list, possibly referring to $interp and $filter... return @list; } =back =head2 Exports and Use Parameters =over 4 =item EXPORTS use SQL::Interpolate::Macro qw(:all); ':all' exports these functions: sql_and, sql_flatten, sql_if, sql_link, sql_or, sql_paren, sql_rel, sql_rel_filter . =back =head1 DEPENDENCIES This module depends on SQL::Interpolate but otherwise has no major dependencies. =head1 DESIGN NOTES =head2 Limitations This macro facilities are still a bit under development, so interfaces could change and may particularly affect you if you are writing your own macros. The utility of macros over just plain SQL has been questioned. A healthy balance can probably be made: use macros only when they are elucidate rather than obscure and when they improve robustness and simplicity of the syntax. =head2 Proposed Enhancements REL(AB,BC) could be expanded into an "x as AB JOIN y as BC on condition" or "x as AB JOIN y as BC USING(...)" Do all major databases support this syntax? The juxtaposition of the JOIN and the linking condition could eliminate the need for the separate LINK(...) macro: SELECT * FROM REL(AB,BC) WHERE A = ? Other table join improvements - support multi-part keys? - support optional automatic inclusion of LINK(...). =head1 CONTRIBUTORS David Manura (L) (author). Feedback incorporated from Mark Stosberg on table linking, SQL LIMIT, and things. =head1 LEGAL Copyright (c) 2004-2005, David Manura. This module is free software. It may be used, redistributed and/or modified under the same terms as Perl itself. See L. =head1 SEE ALSO Other modules in this distribution: L, L, L. Full example code of automatic table linking - Meset::MessageBoard in Meset (L). Dependencies: L. Related modules: L, L, L.