I hope you've gotten the syntax fixed by now so that it's working -- the replies above are clear enough about what the problem is. Once you have it working, you might think about some "stylistic" improvements:
my @getfields = qw/engine/; for my $type ( qw/name lable settings/ ) { for my $num ( 1 .. 4 ) { push @getfields, "$type$num"; } } my $sql = 'select '. join( ',', @getfields ). ' from special_fields WHERE engine IN ('. join( ',', ('?') x scalar @choices ). ') AND ('. join( ' OR ', map { "settings$_ = 'public'" } 1..4 ). ')'; my $sth = $dbh->prepare( $sql ); $sth->execute( @choices );
Notes: (update: having seen jdporter's reply, I have to agree -- his version is much easier to read)

In reply to Re: in, ands, ors in query by graff
in thread in, ands, ors in query by Anonymous Monk

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.