a primary key is used to uniquely identify each row in a table. It can
either be part of the actual record itself , or it can be an artificial
field (one that has nothing to do with the actual record).
A primary key can consist of one or more fields on a table. When multiple
fields are used as a primary key, they are called a composite key.
A Primary key constraint can be defined at various levels:
* Primary key constraint defined at column level
Syntax: <Column Name> <datatype>(<size>) Primary
* Primary key constraint defined at table level
Syntax: Primary key (<Column Name>, <Column Name>)
On Thu, Jun 24, 2010 at 3:03 PM, Joerg Bruehe <Joerg.Bruehe@stripped> wrote:
> Hi David, all!
> David Stoltz wrote:
> > Actually,
> > That table isn't supposed to have a PK, so I removed that, and it
> > works...same effect you suggested.
> Even if you currently don't need a primary key in that table, IMO you
> should still define one. Use some 'id_testresult' column with an
> autoincrement clause, so you need not provide a value.
> Sooner or later you may (I really think: will) feel the need to uniquely
> identify a row, especially to delete it, and a primary key will be very
> helpful then.
> Your original problem was most likely not due to mentioning "primary
> key" but rather to not providing a column name for it.
> Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@stripped
> Sun Microsystems GmbH, Komturstrasse 18a, D-12099 Berlin
> Geschaeftsfuehrer: Juergen Kunz
> Amtsgericht Muenchen: HRB161028
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
Mobile : 91-9987681929
My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat