You could build your update statment dynamically, and prepare it using prepare_cached. That way its only prepared once (for each variation), and you can still take good advantage of placeholders. This is not the tightest example, and is untested, but should serve its purpose: 
my %col;
$col{foo}=1;
$col{bar}=undef;


my %vbph;
my @vbval;
foreach(sort keys %arg){
  if(defined $arg{$_}){
     $vbph{$_}='?';
     push @vbval,$arg{$_};    
  }else{
     $vbph{$_}='NULL';
  }
}
my $sql='update baz set '.
          join ', ',(map{$_.'='.$vb{$_}} sort keys %arg));
my $sth=$dbh->prepare_cached($sql);
$sth->execute(@vbval);

[download]

In reply to Re: DBI Prepared Update and NULLs by lhoward
in thread DBI Prepared Update and NULLs by paulbort

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.