Changes between Version 5 and Version 6 of statusdatabase


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

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v5 v6  
    55* Move project_flights.priority to flights.priority ?
    66* Remove sensor_status.id primary key and use the submit_time as primary key.
     7* In sensors add a boolean to add the logic for "display on status page" therefore in theory we could store other sensor data and it would not be added to another column on the status page.
     8* Rename sensor_status.sensor_id to Rename sensor_status.flight_id
     9* Make primary ticket nullable?
     10* Make sensor_status.username nullable? check data first
     11* Go through and look for reasonable defaults for things.
    712
    813
     
    4954||  || area || Text (variable length) ||  Required  ||  ||
    5055
     56The 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.
     57||||||||||||= flight_sensors Table =||
     58||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     59|| Primary Key || id || Integer(4 Bytes) ||  Required  || Value is automatically generated. ||
     60||  || flight_id || Integer(4 Bytes) ||  Required  || Value is the flight id from the flights table. ||
     61||  || sensor_name ||  ||  Required  || Name of the sensor used, must be in the sensors table ||
     62||  || priority ||  ||  Required  || Processing priority of the data, must be in the processing table. ||
     63||  || priority_offset || Integer(2 Bytes) ||    || Not sure what this is used for ||
     64||  || number_of_flightlines || Integer(2 Bytes) ||    ||  ||
     65||  || completion_time || Real (variable precision 4 Bytes) ||    ||  ||
     66||  || delivery_check_time || Real (variable precision 4 Bytes) ||    ||  ||
    5167
    52 
    53 
    54 
     68The sensor_status page contains all the information about the processing status of the data. Essentially it is kind of an audit trail sort of showing who's done what with the data.
     69||||||||||||= sensor_status Table =||
     70||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
     71|| Primary Key || id || Integer(4 Bytes) ||  Required  || Value is automatically generated. ||
     72||  || sensor_id || Integer(4 Bytes) ||  Required  || Value is the flight_id from the flight_sensors table. ||
     73||  || username || Text (variable length) ||  Required  ||  ||
     74||  || submit_time || Timestamp ||  Required  || Should be omitted from the insert query or explicitly told to use the DEFAULT value as this is the current time / insert time. ||
     75||  || progress || Text (variable length) ||  Required  || Value must be in the progress table. ||
     76||  || notes || Text (variable length) ||    ||  ||
    5577
    5678