Changes between Version 4 and Version 5 of statusdatabase


Ignore:
Timestamp:
Aug 11, 2014 9:51:47 AM (5 years ago)
Author:
tec
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v4 v5  
    1 == Structure of current ARSF Database ==
     1== Structure of new ARSF Database ==
     2
     3'''Things to change in database revision 2'''
     4* Move project_flights.area to flights.area ?
     5* Move project_flights.priority to flights.priority ?
     6* Remove sensor_status.id primary key and use the submit_time as primary key.
     7
     8
     9
    210
    311The database is made up of 9 tables, joined together by relations. See below for a diagram of the database tables and relations
     
    3341||  || data_recieved_on || Date ||  ||  ||
    3442
    35 
    36 
    37 
    38 
    39 
    40 
    41 
    42 
    43 
    44 
     43The project_flights table (in database terms prevents a many-to-many relationship) holds data which allows for a single flight to have more than one project code, the table also contains the priorities for the different project codes and the area that was investigated.
     44||||||||||||= project_flights Table =||
     45||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     46|| Primary Key || flight_id || Integer(4 Bytes) ||  Required  || Value must be in the flights table. ||
     47|| Primary Key || project_code || Text (variable length) ||  Required  || Value must be in the projects table. ||
     48||  || priority || Text (variable length) ||  Required  || Value must be in the priorities table. ||
     49||  || area || Text (variable length) ||  Required  ||  ||
    4550
    4651