No
2015-08-12 19:10:04.541966+02 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?"
2015-08-12 19:10:04.541966+02 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 19:01:34.565284+02 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 20:29:00.38282+02 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?"
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.