Re: Database beginner needs design help
No Problem - My edition says 2nd Edition right on the front under the title....
My Dad once told me a story that I think applies here:
One day two hunters were out searching for their quarry in Africa
and they decided to split up to cover more ground. They also decided
to meet back at the big rock at noon to see what each other had found.
Well, noon came around and the older, more experienced of the hunters
had his quarry down and motioned for the younger hunter to follow him.
After walking for some time they came upon a clearing and the young
hunter saw that the old man did indeed have his game down. It just
happen to be a huge elephant!
On seeing this the young hunter exclaimed, "Are you crazy??!! That
animal is huge! How do you even think you could eat an elephant?"
The older wiser hunter just thought for one moment. Then he calmly
replied, "One bite at a time... just one bite at a time"
My whole point here is - Don't try and think of this project as a huge
elephant that you have to eat all in one sitting... Think of it as a bunch
of little steaks that you cut up into little bites to eat. Break it down into
a bunch of smaller chunks (projects) to accomplish.
Remember that this is a work in progress. It probably will go
through a bunch of changes before you are finished.
There are many uses for the tables in a database. Some are informational,
some are support tables - to ease data entry and
provide consistancy to your users, some are linking tables to provide
for the relationships.
So to answer this requires the knowledge of what you are
trying to accomplish.
Use the book and try and follow the theories in it. He gives very
good examples - The normalization process that Hernandez takes you
through will tell you if you need a "details" support table.
Good luck in the learning process!
Holler back if you have more questions.
-Scott
Originally posted by jweasl
View Post
I'm starting to get confused
One day two hunters were out searching for their quarry in Africa
and they decided to split up to cover more ground. They also decided
to meet back at the big rock at noon to see what each other had found.
Well, noon came around and the older, more experienced of the hunters
had his quarry down and motioned for the younger hunter to follow him.
After walking for some time they came upon a clearing and the young
hunter saw that the old man did indeed have his game down. It just
happen to be a huge elephant!
On seeing this the young hunter exclaimed, "Are you crazy??!! That
animal is huge! How do you even think you could eat an elephant?"
The older wiser hunter just thought for one moment. Then he calmly
replied, "One bite at a time... just one bite at a time"
My whole point here is - Don't try and think of this project as a huge
elephant that you have to eat all in one sitting... Think of it as a bunch
of little steaks that you cut up into little bites to eat. Break it down into
a bunch of smaller chunks (projects) to accomplish.
Remember that this is a work in progress. It probably will go
through a bunch of changes before you are finished.
So I fell like I should have a Machine Details table, Product Details, Purchase Order Details tables as well. Help please?
some are support tables - to ease data entry and
provide consistancy to your users, some are linking tables to provide
for the relationships.
So to answer this requires the knowledge of what you are
trying to accomplish.
Use the book and try and follow the theories in it. He gives very
good examples - The normalization process that Hernandez takes you
through will tell you if you need a "details" support table.
Good luck in the learning process!
Holler back if you have more questions.
-Scott
Comment