Timeline for How can I determine size of database prior to importing from SQL dump?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2021 at 4:01 | comment | added | Rick James |
@AufgeschissenerKunde - These days, 20.5GB is not very big. It seems foolish to truncate strings. There are legitimate "names" (cities, last names, titles, companies, etc) that are longer than 70 characters. On the other hand, it is inefficient to allow 1000 characters for names that will never be that long. I often argue against blindly making everything VARCHAR(255).
|
|
| May 18, 2021 at 0:21 | comment | added | Aufgeschissener Kunde |
What you said about the BIGINTs probably containing lots of small numbers makes a lot of sense. This project is a big, unoptimized mess of too many frameworks and plug-ins mashed together. The administrator interface even truncates string fields for being "too long" after they've already been entered into the database when the user registered!
|
|
| May 18, 2021 at 0:16 | vote | accept | Aufgeschissener Kunde | ||
| May 17, 2021 at 19:38 | history | edited | Rick James | CC BY-SA 4.0 |
added 957 characters in body
|
| May 17, 2021 at 19:20 | history | answered | Rick James | CC BY-SA 4.0 |