For Q.2: In order to avoid race conditions (where you check fo r the record existence in the db, but someone else inserts it before you have a chance of inserting it) you should let the database do the checking.
This is normally done with a constraint (usually a unique index of some sort). You then trap that error in the insert logic. Something like this: 
# Assumes RaiseError is set
eval {
  $dbh->do("insert ....");
};
if($@) {
    # check for the "duplicate insert" error here, and 
    # handle accordingly...
}

[download]

Michael

In reply to Re: Handling Null or Undef values in DBI (and things of those nature)... by mpeppler
in thread Handling Null or Undef values in DBI (and things of those nature)... by data67

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.