View Full Version : Futurequest in 1969
Wassercrats
03-28-2005, 08:23 PM
According to Bekariso's profile (http://www.aota.net/forums/member.php?userid=9), his last activity was 12-31-1969 07:00 PM. I know 1969 is the base date in some time functions in programming, so there might be a bug somewhere, unless Futurequest is older than I thought.
JoeLeBlanc
03-28-2005, 11:24 PM
According to Bekariso's profile (http://www.aota.net/forums/member.php?userid=9), his last activity was 12-31-1969 07:00 PM. I know 1969 is the base date in some time functions in programming, so there might be a bug somewhere, unless Futurequest is older than I thought.
My thinking is that the eariler versions of the forums stored the date differently as of now, that can be also a problem, I don't
think its a BUG per say, but merly a different format of the
date and time or the db in that field is just blank.
I hope I explainned that pretty good. If not I know someone would correct me :rasberry:
Joseph
03-28-2005, 11:27 PM
It was likely something that happened with the move from UBB to vB many years ago. As mentioned, it's not a bug, more like a... easter egg :rasberry:
Randall
03-29-2005, 12:39 PM
more like a... easter egg Hey! Wasser already has an egg. That ain't fair. :ytold:
Randall
Wassercrats
03-29-2005, 02:53 PM
I'll be paying a Futurequest bill in a day or two. I won't claim this egg until I claim the first so my eggs won't be all in one basket.
Andilinks
03-29-2005, 03:34 PM
Entomophobia annoys me. Any date that is inaccurate by ~40 years is a big, fat, glaring, dumb mistake no matter whether the cause is a bug, semi-insect, or pseudo-Easter egg.
Unless you're carbon-dating antiquities from some cave, then being within 40 years is quite accurate enough.
If it is in fact an Easter Egg can Barry claim compound interest on it dating from 1969?
Andi
sheila
03-29-2005, 08:25 PM
My guess is that for some reason the date field in the current database was empty, and that in that case the default date is set to 0, which from Unix time format translates into Dec 31, 1969 UTC (the beginning of Unix time).
Now, why that date field was empty to begin with...I have no idea.
Andilinks
03-29-2005, 08:35 PM
And in 2037 we will replay the Y2K bug, a mere 32 years. Someone being born today may have to fix this...
JoeLeBlanc
03-29-2005, 09:13 PM
And in 2037 we will replay the Y2K bug, a mere 32 years. Someone being born today may have to fix this...
Thats what these 64 bit processors are :-D and its 2038 not 2037. 32-bit unix time won't be able to process time beyond Jan 19 2038 at 3:14:07 AM GMT
Wassercrats
08-07-2005, 05:02 PM
I wonder how this member (http://www.aota.net/forums/member.php?u=1164) fits into this.
vBulletin® v3.6.8, Copyright ©2000-2012, Jelsoft Enterprises Ltd.