SLASHDOT FUCKED UP
http://blogs.securiteam.com/
It’s Y2K, no, it’s 32 bit unix time, no, it’s Slashdot!
Slashdot Posting Bug Infuriates Haggard Admins
http://slashdot.org/articles/06/11/09/1534204.shtml
“it’s like y2k but worse”
I know what you mean. Y2K was supposed to put an end to civilization, but at least we’d have been able to post on slashdot.
“2^24 comments ought to be enough for anyone” — CmdrTaco
Some of you are asking which comment it was that got the cid 16,777,216. The answer is that none did. For redundancy, Slashdot is now running multiple-master replication which skips values for auto-increment. Our db-1 assigns odd-numbered primary key IDs, and db-2 assigns even-numbered. Right now writes are going to db-1 so newly created rows will have only odd IDs.
The comment that got 2**24-1 was this one, if anyone cares.Sorry about the inconvenience, everyone
So is the bug still in the CVS revision of Slash, or was it fixed 5 years ago and Slashdot never applied the patch?
Does this mean that Slashdot is going to denegrate into Digg now?
At least nobody can feed the trolls now!
Of course, in a decent database engine, like PostgreSQL, if you alter a column data type then the indexes are updated to reflect this.