int(11) and unix timestamp

[Jakeman]

What is the biggest number / date that can be stored in a field of type int(11)? Just curious.

:cheeky:

[Dark_Wizard]

Theoretically the largest would be 99999999999 which would produce the date of: Wed, 16 Nov 5138 09:46:39 UTC

[Andreas]

I somewhat doubt we'll use mySQL in year 5138 ^.^

[Dark_Wizard]

Originally Posted by KirbyDE

I somewhat doubt we'll use mySQL in year 5138 ^.^

LOL...agreed. I wonder what it would be like in 5138?

[Xenon]

actually dark wizard is not correct here.

INT datatype is a 32 Bit integer, so if signed, then the biggest value is 2^31 - 1 = 2.147.483.647

the (11) is useless as no int 32 can ahve more than 10 chars.

so to using the calculator gives you '19 Jan 2038' as biggest timestamp.

[Modin]

Yep, that's the "real" y2k scare Xenon

though technically a timestamp is of type LONG not INT, INT's are only 16bits while LONG's are 32bits (on most architectures)

[Jakeman]

So I've got some time before I have to worry.

[Xenon]

Ahh, time flies Jake

@Modin: thechnically LONG is just the short form of LONG INTEGER, so INT is the correct thing here

[Dark_Wizard]

Originally Posted by Xenon

actually dark wizard is not correct here.

INT datatype is a 32 Bit integer, so if signed, then the biggest value is 2^31 - 1 = 2.147.483.647

the (11) is useless as no int 32 can ahve more than 10 chars.

so to using the calculator gives you '19 Jan 2038' as biggest timestamp.

Interesting...hey at least I gave it a shot.

[Xenon]

yay

you cannot be correct everytime

even i make mistakes (at least the others say so ^^)