3 ms·
SQL. >it comes with a number of performance and memory/storage consumption implications. Instead of selecting sum(), CREATE TRIGGER then and update a singleto
by wruza 7y ago
SQL.
>it comes with a number of performance and memory/storage consumption implications.
Instead of selecting sum(), CREATE TRIGGER then and update a singleton on insert. You can even create a view with N recent transactions and catch inserts into it to maintain that N, if you don’t want a full history.