Database Structure Help
Posted by: Ricardo De Nobrega
Date: September 18, 2011 10:42AM

I need help, advice or even a brainstorm with regard to creating the database structure for my website.

I am a Photographer and I primarily focus on horse racing.
The aim of this database will be to provide a service to the horse racing community.

I capture the result of each race that happens throughout the country.
For this I have a little program that allows me to import the racecard.txt and result.txt files and then extract the data to an xls file.

Listed below are samples of the files mentioned above.

You will notice in the xls file is a 2nd worksheet labelled "Table Layout". It lists the current layout and then I've broken it down into more detail using the current headers as tables.

The data works great but it is limited. For example, the "owner" of a horse is a string of owners;How do you assign a horseID to an owner who owns multiple horses and in the same light how do you assign an ownerID to a horse that has multiple owners? Certain owners are also members of a syndicate. Each syndicate has a nominee representative. Also, some owners are breeders and some breeders are owners. Now its getting really confusing as to how to assign what to where, or whether I need to create views to get the data to display the way I want it to, or use the current data as the "source" and then create views. Example: assign an ownerID to the current string of owners and then link that to a table called ownerIndividual and assign the ownerID to the matching individual owners.

Any help, advice or brainstorming on this will be hugely appreciated.

Options: ReplyQuote

Written By
Database Structure Help
September 18, 2011 10:42AM
September 19, 2011 01:24AM
September 22, 2011 04:10PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.