3 ms·
Is there ever a reason to use an INT these days? If you do have a lot of rows, you need BIGINT anyway. If you don't have a lot of rows, the few extra megabytes
by WJW 3y ago
Is there ever a reason to use an INT these days? If you do have a lot of rows, you need BIGINT anyway. If you don't have a lot of rows, the few extra megabytes of disk usage from INT vs BIGINT are unlikely to cause any problems and are probably not even worth thinking about.
- donatj 3y agoA good example of where INT might make sense could be a table of a relatively set size, where other tables with massively more data had a foreign key to it. No chance of overflow, but as a BIGINT it would take a ton of space elsewhere. Even then though, it’s potentially not worth it.
- PaulHoule 3y agoI figure we might run out of UUIDs if we build a Dyson sphere.
- datadrivenangel 3y agoJust do IPv8