Sounds like you set a primary key without setting that key to auto_increment:

testdb> create table foo(id int unsigned not null, bar varchar(32), pr +imary key(id)); Query OK, 0 rows affected (0.01 sec) testdb> insert into foo(bar) values('foo'); Query OK, 1 row affected, 1 warning (0.00 sec) testdb> insert into foo(bar) values('bar'); ERROR 1062 (23000): Duplicate entry '0' for key 1
You will either need to handle the key increment yourself -- or alter the table to make the id auto_increment'ed.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re: Database Error? DBD:MySQL:DB DO failed: Duplicate entry '0' for key '1' at by jeffa
in thread Database Error? DBD:MySQL:DB DO failed: Duplicate entry '0' for key '1' at by jdlev

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.