• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Relational database structure design question

I want to design a relational database to support a dynamic web page for a friend.  The website is about dogs and the database will contain the dog names and all possible competition titles.  I want an end result that allows the user to update the titles (usually multiple titles) a specific dog has earned and then the web page will display the animal's name and all related titles.

I am stuck at having three tables within the DB;
table_DOGS   ---  all dogs breed by breeder
dogs_RegName (PK)
dogs_CallName
<other fields >

table_TITLES  ---  all possible titles
titles_org (PK)
titles_title (PK)
titles_description
<other fields >

table_DogTitles  --  
dogtitles_dogs_RegName
dogtitles_titles_org
dogtitles_titles_title
dogtitles_year

It seems to me I'm creating a many to many situation that I think I don't want.  Is there a better way?
0
ITNESPEO
Asked:
ITNESPEO
1 Solution
 
ldunscombeCommented:
I would actualy suggest an extra table for Breeder ie

tbl_Breeders
tbl_Dogs
tbl_DogTitlesData
tbl_Titles

You would then have a "one to many" relationship from breeders to dogs
a "one to many" relationship from dogs to dogTitlesData
and a "one to one" relationship from dogtitlesdata to Titles.

Provided you set your indexes and primary keys this is actually good design.

Cheers
Leigh
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now