You mentioned using queries and switchboards in my final
project which I'm definitely going to create when I learn how.
The scope of my database has changed a little. Initially I was
just going to make tables of books, but I decided that while
I'm at it I might as well add Movies and TV Series to the mix.
I'm also considering making a table for games since my husband
and I have quite a collection of board and card games. Video
games may get their own table or be added to the game tables.
As I'm still trying to decide that you'll notice I don't have a
game table in my database yet.
I will have tables for books, movies, tv series, and possibly
games by the end of my project. These tables will have useful
information. Major information such as titles, authors, and
genres are included along with more specific information. For
example, my movie table contains a field to enter the length of
the movie so we can see at a glance whether we want to take the
time to watch a particular movie. In the books table I have a
check-box that lets me know whether a book is child-appropriate
or not. I will check (or not check) these boxes as I read so I
can remember what books to recommend to the youth I work with
at church as well as to community members in libraries I may
work in.
Books, Movies, TV series, and Games don't always relate to each
other, but sometimes movies or TV shows are based off of books,
and games are often based off of movies. Thus, I am relating the tables by those things that they are likely to have in common such as book titles. I thought about relating all the tables by genre, but I am allowing myself to apply multiple genres to a single record so I can't relate them across tables. I may change that, but I hate only being able to choose one genre when multiple ones apply. I didn't put very many records into my tables just in case I have to change something major or start all over again to get everything to relate better. As is I had a lot of fun learning how to make simple forms so I could enter the data into the tables faster. I'm looking forward to continuing this coming week.
Saturday, February 14, 2009
Subscribe to:
Post Comments (Atom)

Interesting. I like how you are applying real-life needs to the design of your database. Your relationship idea, while unorthodox, certainly sounds like a good one. I look forward to seeing what you do with this.
ReplyDelete