TIMESTAMP has a resolution of only 1 second. Not good enough as a primary
key for most applications. You may want an auto_incrementing int field (or
bigint depending on the size of your data) and make that your primary key.
Only the first TIMESTAMP column is automatically updated with the update
Scott Fletcher wrote:
I read some articles that the use of SQL's TIMESTAMP in a table is use
for recording the actual date/time that the row was inserted and for
row(s) that is/are updated. I'm a little troubled by that because I
want a table with a timestamp in the first column to be the transac
