Timeline for Alternatives to running query for rarely changed data everytime on large table
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2018 at 7:20 | comment | added | JaggenSWE | The main issue regarding normalization is that I'm sadly not entitled to change the database structure itself in this project. It's basically a replicated and indexed version coming out of another system, but even so it tends to be a bit on the heavy side for presenting in a web application. Thanks for your input though, appreciate it. :) I'll have a look at caching | |
| Apr 5, 2018 at 22:25 | comment | added | jpmc26 | Note that it still makes sense to have an index even after normalizing. For one, there should probably be a unique constraint on the name. For two, I suspect the database could make use of the index already being sorted. | |
| Apr 5, 2018 at 14:33 | history | edited | RBarryYoung | CC BY-SA 3.0 |
added 529 characters in body
|
| Apr 5, 2018 at 14:26 | history | answered | RBarryYoung | CC BY-SA 3.0 |