From: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> |
---|---|
To: | Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Approach to Data Summary and Analysis |
Date: | 2014-04-15 12:37:03 |
Message-ID: | 20140415143703.1028f1e903cec95361bb68cb@wanadoo.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 14 Apr 2014 15:22:13 -0700
Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> wrote:
Hi Robert,
> But then I lose a bunch of data like the TIMESTAMPTZ of the call, answer,
> connection, etc. Btw, currently these tables never need to be UPDATEd. They
> are immutable in the current design.
Yes, but you wrote :
>Occasionally I will want to know things like "When was the last time a user
>answered a call" or "How many times has a user been called".
With your schema, you would have to query several tables each time. Queries will get messy in a hurry, updates and DDL changes too.
> And in the end I'm not sure how the
> proposal of one table and a state that is updatable changes the basic
> thrust of the question. For example, getting last call, last answered,
> total called, total answered. If the state of a call transitions from
> called to answered then making it a field loses all the data with the
> previous state, make sense?
>
If you need this, you can use a schema that accommodates it.
(off the top of my head, insert a new record instead of altering an existing one, and create a hierarchy with parent records that point to an original call, may be with a 'parent' field and recursive queries. You probably have many requirements that I'm not aware of, but this one can be met)
--
Salutations, Vincent Veyron
http://marica.fr
Gestion des contentieux juridiques, des contrats et des sinistres d'assurance
From | Date | Subject | |
---|---|---|---|
Next Message | Robert DiFalco | 2014-04-15 14:21:58 | Re: Approach to Data Summary and Analysis |
Previous Message | Willy-Bas Loos | 2014-04-15 11:08:24 | [GENARAL] round() bug? |