Flutterby™! : No

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics


2015-08-12 17:10:04.541966+00 by Dan Lyke 2 comments

No: "Will we ever have more than 2^32 rows in that database table?". Yes: "Is there any good reason to *not* use 64 bit row IDs?"

[ related topics: Databases Furniture ]

comments in ascending chronological order (reverse):

#Comment Re: No made: 2015-08-14 17:01:34.565284+00 by: meuon

My default is a bigint for any row id, unless I am sure that the table will not get more than 10 rows.

bigint: 8 bytes. max value, if "signed" ranges from 0 to: 18446744073709551615

#Comment Re: No made: 2015-08-17 18:29:00.38282+00 by: Dan Lyke

Yep. At some point someone used a MySQL MEDIUMINT for a table that... well... and we're having conversations about whether we'll ever hit 4 billion rows and I'm saying "we may not, but there are outside scenarios where in 15 years we might, disk space is cheap, why are we having this discussion?"