Timeline for Is this db/table structure sensible?
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2015 at 1:30 | comment | added | acj | Thanks for the tips, this might save us some db space on amazon :) Amazon does the backup and we archiv older years of data from time to time. Right now its not that of a performance problem, more like a handling through rails inconvenience as i tried to point out. So basically im collecting arguments to convince them to switch to one big table, perhaps with transparent (at least for RoR) partioning/sharding - but better more native handling through RoR as a beneficial result. | |
| Jun 12, 2015 at 22:55 | history | answered | Rick James | CC BY-SA 3.0 |