Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.databases.ms-sqlserver > #899

Re: relational design question

From "Fred." <ghrno-google@yahoo.com>
Newsgroups comp.databases.ms-sqlserver
Subject Re: relational design question
Date 2012-01-12 06:21 -0800
Organization http://groups.google.com
Message-ID <12044559.466.1326378113904.JavaMail.geo-discussion-forums@yqni15> (permalink)
References <390061ca-db22-4194-a2de-fd1f19e76740@do4g2000vbb.googlegroups.com>

Show all headers | View raw


I think you need to think in problem terms
for a while before you go back to data.  What
is obvious is that there can be muliple
educational reports from the same or over the
years different sources, and they can be 
redundant or in conflict.

What you really need to come down to is a
set of education records for each nominee
with conficts and redundancies resolved.

So my shot would be that you really need
two education tables, one for reports
where each record contains a foreign key
to the reporting nomination, and one for
resolved records where each record
contains the nominee_id, which I assume
remains the same from year to year.

Of course if you are going to resolve 
these conficts in the data entry process
you can drop the table for educational
reports.  If entering from paper, you
will need to file the paper anyhow.

Fred.

Back to comp.databases.ms-sqlserver | Previous | NextPrevious in thread | Find similar


Thread

relational design question livefree75 <jpittman2@gmail.com> - 2012-01-11 07:24 -0800
  Re: relational design question "Fred." <ghrno-google@yahoo.com> - 2012-01-12 06:21 -0800

csiph-web