Timeline for Indexed Complex View
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2015 at 20:21 | comment | added | Steven | It "feels" like this indexing is a bad idea in my case. I appreciate these options and I am investigating others. | |
| Nov 13, 2015 at 20:20 | vote | accept | Steven | ||
| Nov 13, 2015 at 4:26 | comment | added | Hannah Vernon♦ | @MichaelGreen Well done on that retort, and you made a good point! | |
| Nov 12, 2015 at 18:21 | comment | added | Michael Green | I was hoping to make the OP aware of an alternative he may like to consider and evaluate in his particular circumstances, with his data, load, SLA, use cases etc. etc. While cataclysmic performance should be avoided, apocalyptic stale data is a circumstance which may also be worthy of some cogitation, I would posit. | |
| Nov 12, 2015 at 16:22 | comment | added | Hannah Vernon♦ | @MichaelGreen - are you suggesting to put the code in my answer into an "after trigger"? That might be cataclysmic for performance, depending on how often writes occur, and how many rows exist in the table. | |
| Nov 12, 2015 at 0:48 | comment | added | Michael Green | Add triggers to the underlying tables if you're prepared to sacrifice write performance for more up to date aggregates. | |
| Nov 11, 2015 at 17:15 | history | edited | Hannah Vernon♦ | CC BY-SA 3.0 |
added 336 characters in body
|
| Nov 11, 2015 at 16:34 | history | edited | RLF | CC BY-SA 3.0 |
Re-edit formatting.
|
| Nov 11, 2015 at 16:04 | history | edited | Hannah Vernon♦ | CC BY-SA 3.0 |
added 172 characters in body
|
| Nov 11, 2015 at 16:03 | history | edited | RLF | CC BY-SA 3.0 |
formatted for Max Vernon
|
| Nov 11, 2015 at 16:01 | history | answered | Hannah Vernon♦ | CC BY-SA 3.0 |