Google Blogoscoped


Slashdot Hits Comments Limit  (View post)

Roger Browne [PersonRank 10]

Friday, November 10, 2006
16 years ago3,859 views

> I used Int at Google Blogoscoped, so post away
> – we still have 4,294,913,133 comments to go

I think you'll find that you only have space for 2,147,483,647 comments (assuming we're talking about SQL INT here, which is signed).

Philipp Lenssen [PersonRank 10]

16 years ago #

It's unsigned now, thanks for pointing out :)
(It's a dropdown selection in PHPMyAdmin.)

Roger Browne [PersonRank 10]

16 years ago #

Anyway, 2,147,483,647 comments out to be enough for anyone...

Ryan [PersonRank 0]

16 years ago #

so wait, I shouldn't have used "blob" for that field???

Haochi [PersonRank 10]

16 years ago #

That's a lesson for start-ups – plan for the future.

kmike [PersonRank 1]

16 years ago #

Hmm, why do everyone get it wrong? It's all explained in the story, but looks like no one reads TFA now, just the sensationalist Digg summaries...

The comment field was already unsigned (2^32), it's the parentid field which was mediumint. Commenting wasn't down during the conversion, only the threading – basically bringing the features down to the level of blog commenting (such as this one).

alek [PersonRank 10]

16 years ago #

kmike beat me to it – there are actually tons of comments even on the /. thread where they say they overflowed on the parentid. Was kinda funny seeing everythng a single level deep for a day.

telcogod [PersonRank 1]

16 years ago #

I ran a cabs bill the other day for 5 million dollars, where you multiply minutes of use * 600 to meet OBF guidelines, and had to change the datatype to bigint.

Forum home


Blog  |  Forum     more >> Archive | Feed | Google's blogs | About


This site unofficially covers Google™ and more with some rights reserved. Join our forum!