Changes between Version 3 and Version 4 of statusdatabase


Ignore:
Timestamp:
Aug 8, 2014 9:57:01 AM (5 years ago)
Author:
tec
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v3 v4  
    33The database is made up of 9 tables, joined together by relations. See below for a diagram of the database tables and relations
    44
    5 The PI table is made up of the PI's name, address and their email address. The table has and internal field called 'id' which is filled in automatically and is referred to whenever a PI is linked to a project code.
    6 ||||||||||||= PI Table =||
     5The PI table is made up of the PI's name, address and their email address. The table has and internal field called 'id' which is filled in automatically and is referred to whenever a PI is linked to a project code. If you try and delete a PI, and that PI still has project_codes referring to the PI then the Database will prevent you deleting the PI.
     6||||||||||||= pi Table =||
    77||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
    8 || Primary Key || id || Integer(4 Bytes) || Required || Value is automatically generated ||
    9 ||  || pi_name || Text (variable length) || Required ||  ||
     8|| Primary Key || id || Integer(4 Bytes) ||  Required  || Value is automatically generated. ||
     9||  || pi_name || Text (variable length) ||  Required ||  ||
    1010||  || address || Text (variable length) ||  || Not required as may not be known at time of entry. ||
    1111||  || email || Text (variable length) ||  || Not required as may not be known at time of entry. ||
    1212
     13The projects table contains all the project codes and what PI relates to which project code. Many project codes can relate to one PI.
     14||||||||||||= projects Table =||
     15||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     16|| Primary Key || project_code || Text (variable length) ||  Required  ||  ||
     17|| Foreign Key || pi_id || Integer(4 Bytes) ||  Required  || The PI's ID from the pi table. ||
     18||  || summary || Text (variable length) ||  ||  ||
     19||  || eufar_code || Text (variable length) ||  ||  ||
     20||  || objective || Text (variable length) ||  ||  ||
    1321
    14 
    15 
    16 
    17 
     22The flights table contains the information about one flight. So if two flights were made in one day, then there would be two entries in the flight table.
     23||||||||||||= flights Table =||
     24||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     25|| Primary Key || flight_id || Integer(4 Bytes) ||  Required  || Value is automatically generated. ||
     26||  || flight_date || Date || Required || The date that the flight took place ||
     27||  || primary_ticket || Integer(2 Bytes) || Required || Primary ticket id for trac ||
     28||  || kml_file_location || Text (variable length) ||  ||  ||
     29||  || data_location || Text (variable length) ||  ||  ||
     30||  || sortie || Text (variable length) || Required || The letter to differentiate multiple flights flown on one day ||
     31||  || notes || Text (variable length) ||  ||  ||
     32||  || secondary_tickets || Integer(2 Bytes) Array ||  ||  ||
     33||  || data_recieved_on || Date ||  ||  ||
    1834
    1935