Changes between Version 5 and Version 6 of Normalization


Ignore:
Timestamp:
07/21/25 23:59:31 (8 days ago)
Author:
221514
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Normalization

    v5 v6  
    44
    55Given the relational schema we already created in earlier sections of this project, the database can be made so it is represented in exactly 1 relation with all the attributes from every relation concatenated together. Of course, duplicates would be removed by doing this which is not a problem.
    6 
    76Let R be the relation just described:
    8 {{{R(n_tickets,vehicle_id,route_id,latitude,child_disc,rating,free_seats,date,days_active,acc_email,plate_num,person_surname,years_experience,trip_id,ticket_id,company_embg,account_id,time_stop,model,time_purchased,payment_id,total_price,person_name,student_disc,company_name,brand,account_email,location_id,child_embg,longitude,loc_name,two_way,capacity,status,parent_embg,date_purchased,password,review_description,year_manuf,review_id)}}}
     7{{{
     8R(
     9    n_tickets,vehicle_id,route_id,latitude,
     10    child_disc,rating,free_seats,date,
     11    days_active,acc_email,plate_num,person_surname,
     12    years_experience,trip_id,ticket_id,company_embg,
     13    account_id,time_stop,model,time_purchased,payment_id,
     14    total_price,person_name,student_disc,
     15    company_name,brand,account_email,location_id,
     16    child_embg,longitude,loc_name,two_way,
     17    capacity,status,parent_embg,date_purchased,
     18    password,review_description,year_manuf,review_id
     19)
     20}}}
    921
    1022== 1.1. Initial functional dependencies: ==