Databases

Today we talked about database and the different kinds that exist, the goals of databases, and about queries. When i thought about it, the recipe ipod application is really a database at its core, since basically it will store recipes and present them when you ask for it. the recipe ipod itself does more than just that, but the application behaves as a database should. Think of using itunes, it stores a huge amount of information, users can do quick searches, and based on what the user searches for it can eliminate things from its search. Since the recipe ipod application is modeled after itunes, it too would be able to do all these things. It would be a relational database, since it would be organized by keys such as what the recipe makes, type of cuisine, and difficulty level.

In order to do queries efficiently there needs to be a primary key, this presents a challenge, since my immediate thought was to have the primary key be the what the recipe makes (ex: apple Pie) but you can have more than one apple pie recipe. So each recipe in the recipe ipod application will be assigned a number that helps to distinguish it from ever other recipe there is.