I guess the table doesn't have a primary key? Also you should use RaiseError or else check the status of every DBI statement. Anyway you're probably being redundant by specifying 'where rowid = .. and exe_c = ..'. And you can still use placeholders(psuedocode ahead):
my $dbh = DBI->connect('...', 'user','passwd',
 {PrintError=>0, RaiseError=>1});
my $sql = <<EOT;
select ... from .. where exe_c = 'N'
EOT
my $sel_h = $dbh->prepare($sql);
$sql = <<EOT;
update ... set exe_c = 'N' where rowid = ?
EOT
my $upd_h = $dbh->prepare($sql);
$sel_h->execute;
$sel_h->bind_columns(...);
while ($sel_h->fetch) {
 ...
 $upd_h->execute($rowid);
}
$dbh->disconnect;

[download]
------------
ooo  O\O  ooo tilly was here :,(

In reply to Re: Re: Re: Re: Placeholders, safety and the relative unimportance of efficiency by runrig
in thread SQL in Perl and setting variables by Zo

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.