On Thu, 23 Jul 2015, Melvin Davidson wrote:
Does this help?
Melvin,
Yep.
After pondering David's response I recognized my error: I had the permit
table as the center of the relationships when it should be the conditions
table. As you wrote, permits, parameters, and locations all feed the
Does this help?
CREATE TABLE permits
(
permit_number bigint,
...,
other_columns ,
...,
CONSTRAINT permits_pk PRIMARY KEY (permit_number)
);
CREATE TABLE parameters
(
permit_number bigint,
parameter varchar(50),
...,
other_columns ,
...,
CONSTRAINT parameters_pk PRIMARY KEY (permit_number, paramet
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 cr
On Thu, Jul 23, 2015 at 3:06 PM, Rich Shepard
wrote:
> While designing the schema for a new application have become
> high-centered
> and stuck relating some many-to-many tables. Fresh eyes and suggestions are
> needed on how to create many-to-many association tables among these five.
>
> Tab
