Changes between Version 23 and Version 24 of statusdatabase


Ignore:
Timestamp:
Aug 20, 2014 10:29:11 AM (5 years ago)
Author:
tec
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v23 v24  
    4040||  || email || Text (variable length) ||  || Not required as may not be known at time of entry. ||
    4141
    42 The projects table contains all the project codes and what PI relates to which project code. Many project codes can relate to one PI.
     42The projects table contains all the project codes and what PI relates to which project code. Many project codes can relate to one PI. If one tries to delete a PI and they have a project code related to them, the database will say nah.
    4343||||||||||||= projects Table =||
    4444||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     
    6262||  || data_recieved_on || Date ||  ||  ||
    6363
    64 The 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.
     64The 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. If a flight is deleted then a row in this table is automatically deleted, if you try to delete a PI that is linked to flights the database will prevent you from doing so.
    6565||||||||||||= project_flights Table =||
    6666||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     
    7070||  || area || Text (variable length) ||  Required  ||  ||
    7171
    72 The flight_sensors table contains a row for every sensor that is used on the flight. Store information about how many flight-lines are flown for that sensor and contains the time it has taken to complete the latest delivery check, and time it has taken to complete the processing of the flight sensor data.
     72The flight_sensors table contains a row for every sensor that is used on the flight. Store information about how many flight-lines are flown for that sensor and contains the time it has taken to complete the latest delivery check, and time it has taken to complete the processing of the flight sensor data. A row in the flight sensors table will be automatically deleted if the flight or sensor it linked to is deleted.
    7373||||||||||||= flight_sensors Table =||
    7474||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     
    9292||  || notes || Text (variable length) ||    ||  ||
    9393
    94 The priorities table contains the priority name, the numeric value of the priority and the friendly description of the priority.
     94The priorities table contains the priority name, the numeric value of the priority and the friendly description of the priority. If one tried to delete a priority that is in use the database will just say "nah mate not happening".
    9595||||||||||||= priorities Table =||
    9696||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     
    9999||  || description || Text (variable length) ||  Required  || Friendly description of the priority. ||
    100100
    101 The progress table contains the progress name, the numeric value of the progress and the friendly description of the progress.
     101The progress table contains the progress name, the numeric value of the progress and the friendly description of the progress. If a flight status uses a progress value deleting it will not work.
    102102||||||||||||= progress Table =||
    103103||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||