These were my reasons exactly. I was originally writing a method that would check for pre-existing key and then present options, etc. but was hoping to keep the process as simple as possible for the end user... You know, if they enter the same ISBN twice, it just uses the latest entered data... Transparent to the user. I came across the DUPLICATE KEY thing while browsing and thought maybe I could shoehorn it into my needs... That's why I asked for how people were using it before I showed my own or my reasons... I suppose it makes a little more sense now.

I guess I can still make it transparent to the user, it'll just require more code for the system... Not really a big deal.

I appreciate your input though,
cidaris

In reply to Re: Re^3: MySQL and Duplicate Keys by cidaris
in thread MySQL and Duplicate Keys by cidaris

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.