Unless I missed something I think there are only 4 possiblities.

my $queries = (
"SELECT * FROM or_mod;"
"SELECT * FROM or_mod WHERE upper(component) = upper(?)";
"SELECT * FROM or_mod WHERE upper(env)       = upper(?)";
"SELECT * FROM or_mod WHERE upper(component) = upper(?) AND 
                           upper(env)       = upper(?)";
);
my $sth; my @bind;
if (defined($query{env}) &&(defined $query{component}) {
   $sth = $dbh->prepare($queries->[3]);
   $sth->execute($query{component}, $query{env});
} elsif ( defined ($query{env}) ) { 
   $sth = $dbh->prepare($queries->[2]);
   $sth->execute($query{env});
} elsif ( defined ($query{component}) ) {
   $sth = $dbh->prepare($queries->[1]);
   $sth->execute($query{component});
} else {
   $sth = $dbh->prepare($queries->[0]);
   $sth->execute;
}

[download]

I'm not entirely sure that is much better than dynamicaly generating them, or better at all for that matter. In fact I think the dynamic solution is better because it is dynamic. BTW newer MySQL caches all queries whether you ask or not, I don't know if that holds for bound queries as well. If it does then as long as you are binding, even if it seems lame for this single call, it will give you benefits in the long run.


___________
Eric Hodges

In reply to Re^2: Looking for neater solution with dynamic query by eric256
in thread Looking for neater solution with dynamic query by pg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.