From: | Raymond O'Donnell <rod(at)iol(dot)ie> |
---|---|
To: | Ketema Harris <ketema(at)ketema(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: View vs Constantly Updated Table |
Date: | 2008-12-15 16:25:57 |
Message-ID: | 49468515.2000904@iol.ie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 15/12/2008 16:14, Ketema Harris wrote:
> if i have a "column" that is a calculation, say a bank balance -> sum of
> all the debits and credits...is it more efficient to make a view that
> executes the underlying calc query doing the math, or to create a table
> that has a column called balance that is updated for each transaction?
>
> so in the end "select balance from view" or "select balance from table" ?
It would depend on how much calculation is involved in calculating the
balance..... If you had to query tens of millions of rows to get the
balance, I'd imagine you'd do better to have a trigger updating the
balance every time a row is inserted into the account ledger table.
If there's only a small number of rows to be queried, then it's easier
and probably more robust to do the calculation in a view or a function.
I've done this with ledger containing about 500 rows with no noticeable
delay (on my laptop).
Ray.
------------------------------------------------------------------
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
rod(at)iol(dot)ie
Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals
------------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Rich | 2008-12-15 16:27:39 | Re: View vs Constantly Updated Table |
Previous Message | Ketema Harris | 2008-12-15 16:14:20 | View vs Constantly Updated Table |