From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Schema Help Needed To Get Unstuck |
Date: | 2015-07-24 00:35:20 |
Message-ID: | alpine.LNX.2.11.1507231733220.13736@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 23 Jul 2015, David G. Johnston wrote:
> Conditions <- (Permit + Location + Parameter + Frequency + Temporal (from,
> until))
> Monitoring <- (Condition + Event)
>
> While you may require additional modelling tables to support your user
> interface (i.e., picking valid combinations of PeLoPa when creating a new
> condition) the fundamental concept is that each permit+location+parameter
> combination needs to be monitored during a given period (temporal) at a
> given frequency in that period. Every time that combination generates a
> number you combine the "Condition" with the event (data + time) and add the
> result to the monitoring table.
>
> Active combinations of permits, locations, and parameters can be directly
> derived from the conditions table. The temporal fields facilitate history
> generation.
David,
This is what I was working to achieve, but did not have the details
straight. I'll ponder this and make sure I set the proper FKs on the
appropriate tables.
Thanks,
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2015-07-24 00:37:17 | Re: Delete rule does not prevent truncate |
Previous Message | Adrian Klaver | 2015-07-24 00:27:17 | Re: Delete rule does not prevent truncate |