340
edits
Maintenance DEV: Difference between revisions
→On-The-Fly Updating / Triggers
No edit summary |
|||
| Line 94: | Line 94: | ||
The question here is whether the additional load these on-the-fly updates impose on the database might be a problem. | The question here is whether the additional load these on-the-fly updates impose on the database might be a problem. | ||
One approach to realize this with acceptable work effort required, would be a number of database triggers and corresponding PL/pgSQL functions which transparently update all relevant counters and stats. | |||
One approach to realize this with acceptable work effort required, would be a number of database triggers and corresponding PL/pgSQL functions which transparently update all relevant counters and stats. This could however lead to some performance issues, i.e. think about a user who deletes an entire anime with 100 eps from his mylist. This would yield at least 100 trigger invocations for any listtb based trigger which updates user stats. So instead of decreasing the users file count by 100 in one action, it would effectively be decreased by 1, 100 times. | |||
=== Read-Only database slave for stats work === | === Read-Only database slave for stats work === | ||