Comments on: 4294967295 and MySQL INT(20) Syntax Blows

By: unska

unska — Tue, 08 Mar 2011 07:53:51 +0000

Howcome you didn’t use BIGINT? Wouldn’t that helped you in the first place?

By: Ennuyer.net » Blog Archive » Rails Reading January 26 2010

Ennuyer.net » Blog Archive » Rails Reading January 26 2010 — Tue, 26 Jan 2010 22:32:27 +0000

[...] 4294967295 and MySQL INT(20) Syntax Blows – Laughing Meme [...]

By: A quote from Kellan Elliott-McCrea | BlogHalt.com

A quote from Kellan Elliott-McCrea | BlogHalt.com — Tue, 26 Jan 2010 11:19:36 +0000

[...] – Kellan Elliott-McCrea [...]

By: Richard Crowley

Richard Crowley — Mon, 25 Jan 2010 19:21:03 +0000

What do folks honestly think the 11 in int(11) means? I’ve long since stopped using that notation, simply saying int, int unsigned, bigint unsigned, etc.

By: Kellan

Kellan — Mon, 25 Jan 2010 17:52:40 +0000

@Mark I'm excited!

@Charles well then you'll just have to take my word for it won't you?

By: Charles

Charles — Mon, 25 Jan 2010 17:49:32 +0000

Funny thing is, when I told this story to folks last week, this caught them by surprise. Sophisticated engineers, some of whom had deployed quite large MySQL backed sites.

I’d question the sophisticatedness of any developer that hasn’t read the MySQL manual pages on numeric types, in which the maximum storage size of each numeric type is laid out: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html

By: Mark Atwood

Mark Atwood — Mon, 25 Jan 2010 17:06:43 +0000

The DrizzleDB fork of MySQL addresses this issue in a couple of different ways. One, the 24bit INT has been removed. Don’t use it, even in MySQL. It’s dumb, and it’s slow, and the code that implements it is a crawling horror. Two, display sizes have been removed. Display hints are something that the application or presentation layers should worry about, not the database server.