Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #898 > unrolled thread
| Started by | livefree75 <jpittman2@gmail.com> |
|---|---|
| First post | 2012-01-11 07:24 -0800 |
| Last post | 2012-01-12 06:21 -0800 |
| Articles | 2 — 2 participants |
Back to article view | Back to comp.databases.ms-sqlserver
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
| From | livefree75 <jpittman2@gmail.com> |
|---|---|
| Date | 2012-01-11 07:24 -0800 |
| Subject | relational design question |
| Message-ID | <390061ca-db22-4194-a2de-fd1f19e76740@do4g2000vbb.googlegroups.com> |
Hi - I have a tool that allows managers to nominate their fellow employees for an award. Part of the nomination is specifying the education of an employee. This data can change year to year, and I want to keep track of the data as it existed in each year. I have a nominations table: * nomination_id year candidate_id nominator_id And I have an education_entries table: * ee_id school year degree And I have a nom_education_entries table: * nom_id (FK to nominations.nomination_id) * ee_id (FK to education_entires.ee_id) My intent is for each education_entries row to be able to be used for multiple nominations, but for only one employee. I don't want nominations for different employees to use the same education_entries row. What's the best way to alter the design of this to do what I need?
[toc] | [next] | [standalone]
| From | "Fred." <ghrno-google@yahoo.com> |
|---|---|
| Date | 2012-01-12 06:21 -0800 |
| Message-ID | <12044559.466.1326378113904.JavaMail.geo-discussion-forums@yqni15> |
| In reply to | #898 |
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.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.databases.ms-sqlserver
csiph-web