Re: Updating the SQL key value

I will add a autonumbering PK

Auto-numbered synthetic primary keys are the root of all evil. They usually
indicate a lazy approach to database design. There is almost always a
natural column or combination of columns that can be used as a primary key
without the need to add an extra, redundant numerical column which doesn't
contain any useful information.

Assuming that the you never plan on having two events that occur
concurrently, your "order" column is a perfect natural candidate key.

I disagree, if the nature of that key is such that insertion or deletion
of a record requires re-numbering of other records. I believe the OP wanted
something so that the next upcoming event was *always* numbered 10.
If it's acceptable at some point that the events in the table are numbered
85123, 85127, and 85136, that's fine.

(Though it's a little poorly named, given that ORDER is a SQL keyword.)
.

Relevant Pages

  • Re: Updating the SQL key value
    ... Auto-numbered synthetic primary keys are the root of all evil. ... indicate a lazy approach to database design. ...
    (comp.lang.php)
  • Re: Advanced SQL
    ... For an overview to data modeling and database design. ... "The definition of second normal form states that only tables with composite ... primary keys can be in 1NF but not in 2NF" ...
    (comp.databases.theory)