Should I use a big INT or regular INT in MySQL to store a timestamp?

mysql integer biginteger
JasonDavis picture JasonDavis · Jan 8, 2010 · Viewed 15.8k times · Source

Should I be using a big integer or a regular integer in MySQL to store a timerstamp in? I plan on storing it in an INT and not the built in timestamp or datetime so which INT type should I use?

Answer

zmbush picture zmbush · Jan 8, 2010

Int would roll over to a negative in 2038 (if you are using UNIX timestamp): http://en.wikipedia.org/wiki/2038_problem.

so BIGINT is probably the safest choice

Related questions

What is the difference between tinyint, smallint, mediumint, bigint and int in MySQL?

What is the difference between tinyint, smallint, mediumint, bigint and int in MySQL? In what cases should these be used?

Read More
MySQL Error 1264: out of range value for column

As I SET cust_fax in a table in MySQL like this: cust_fax integer(10) NOT NULL, and then I insert value like this: INSERT INTO database values ('3172978990'); but then it say `error 1264` out of value for column …

Read More
What is the biggest ID number that autoincrement can produce in mysql

I have an database that is rapidly filled with data we talk about 10-20k rows per day. What is a limit of an ID with and autoincrement option? If ID is created as INTEGER then I can do max …

Read More