2/10 – 2/15

2/10 Friday 12:30-1

Talked about Paul’s programming project with Jon Cates. Went over requirements for the site and priorities.

 

2/14 Tuesday 12:30 – 5:30

Setting up membership for Association for Computing Machinery, has a lot of books in it about databases, php, java. The languages and concepts that will be used for the project.

Researching databases. Read about different types of database engines. Don’t know if separate engines will be necessary for the project.

Paul’s previous client for programming came over. I listened in on them discussing the features of the program they wanted. They decided that everything on the contract was finished, so they gladly took the program on their USB and thanked Paul. I asked Paul if I could see the contract for an idea of what a freelance programming contract might look like, and Paul gladly showed me.

 

2/15 Wednesday 7-11pm took class on database for paul’s web project. Here are some notes:

rows -> records
columns -> fields
values -> values are where records and fields meet
record set ->  queries pull from multiple tables and combine them into a record set.
aka: query set, result, query result.
dms: software that keeps and orders a database
eg: mysql, oracle

mysql: more well suited for web database
oracle: more well suited for cooporate databse

->securty
->backing up redundant

->rdbms, relational database management system
-> management that focuses on related tables.

set up as servers or files
mysql, oracle, sqlserver

file database
msacess, sqlight

Database servers
Databases
Tables
Queries
Security
users

Normalization
rules for making a database
1. First Form.
->choice of key attributes needs to be unique
->order of records doesn’t matter
->each field must be a unique categorization
->each record/field intersection contains only one value
2. Second Form.
->all non key fields in the table must be dependent on ALL key fields
PART | WAREHOUSE | quantity | warehouse-address
3. Third Form.
->all non key fields are dependent exclusively on the key
wrong: ID | last name | first name | address | city | state | zip

correct: ID | last name | first name | address | zipID(foreign key)
ID | zip | city | state
4. Fourth Form.
->record type should not contain 2 or more independent multivalued facts about an entity.

wrong:
EMPLOYEE | SKILL | LANGUAGE

ID | EMPLOYEE | SKILL | LANGUAGE
——————————-
| EMPLOYEE | SKILL | LANGUAGE |
|———-+——-+———-|
| Smith    | cook  | French   |
| Smith    | cook  | German   |
| Smith    | cook  | Greek    |
| Smith    | type  | French   |
| Smith    | type  | German   |
| Smith    | type  | Greek    |
——————————-

| EMPLOYEE | SKILL | LANGUAGE |
|———-+——-+———-|
| Smith    | cook  |          |
| Smith    | type  |          |
| Smith    |       | French   |
| Smith    |       | German   |
| Smith    |       | Greek    |
——————————-

correct:
Employee     | skill
Smith        | Cook
Smith        | type

Employee     | Language
Smith        | French
Smith        | German
Smith        | Greek

5. Fith Form.
->
wrong
—————————–
| AGENT | COMPANY | PRODUCT |
|——-+———+———|
| Smith | Ford    | car     |
| Smith | Ford    | truck   |
| Smith | GM      | car     |
| Smith | GM      | truck   |
| Jones | Ford    | car     |
| Jones | Ford    | truck   |
| Brown | Ford    | car     |
| Brown | GM      | car     |
| Brown | Totota  | car     |
| Brown | Totota  | bus     |
—————————–

correct
——————-   ———————   ——————-
| AGENT | COMPANY |   | COMPANY | PRODUCT |   | AGENT | PRODUCT |
|——-+———|   |———+———|   |——-+———|
| Smith | Ford    |   | Ford    | car     |   | Smith | car     | Fifth
| Smith | GM      |   | Ford    | truck   |   | Smith | truck   | Normal
| Jones | Ford    |   | GM      | car     |   | Jones | car     | Form
| Brown | Ford    |   | GM      | truck   |   | Jones | truck   |
| Brown | GM      |   | Toyota  | car     |   | Brown | car     |
| Brown | Toyota  |   | Toyota  | bus     |   | Brown | bus     |
——————-   ———————   ——————-

We made a database structure for the project, but I’m not sure Paul would want me to post it here. Will talk about that database with paul tomorrow.

0 Responses to “2/10 – 2/15”


  • No Comments

Leave a Reply

You must be logged in to post a comment.