Changes between Version 25 and Version 26 of statusdatabase


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

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v25 v26  
    22
    33'''Things to change in database revision 3'''
     4* DOCUMENT SQL QUERIES
     5* need trigger for when last status is gone clear up flight sensors table.
     6* order/order.php page should be created too, this gives simple overview of order in which things should be done when they are not required.
     7* ~~priorities and progress tables, make fields unique?~~
     8* ~~Remove sensor_status.id primary key and use the submit_time as primary key.~~
     9* ~~Make sensor_status.username nullable? check data first~~
     10* ~~Go through and look for reasonable defaults for things.~~
     11* ~~See if progress view / order view is necessary~~.
     12* Determine search stuff properly. Do once progress view is sorted, probably use get variables.
     13* Make objects for things like PIs, Flights etc...
    414* ~~make flights ondelete cascade.~~
    515* ~~make sensor_status delete cascade from flight sensor id~~
    6 * DOCUMENT SQL QUERIES
    716* ~~change sensor_status.flight_id to sensor_status.flight_sensor_id~~
    8 * need trigger for when last status is gone clear up flight sensors table.
    917* ~~fix spelling boresite -> boresight~~
    10 * priorities and progress tables, make fields unique?
    1118* ~~Move project_flights.area to flights.area~~
    1219* ~~Move project_flights.priority to flights.priority~~
    13 * Remove sensor_status.id primary key and use the submit_time as primary key.
    1420* ~~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.~~
    1521* ~~Rename sensor_status.sensor_id to Rename sensor_status.flight_id~~
    1622* ~~Make primary ticket nullable~~
    17 * Make sensor_status.username nullable? check data first
    18 * Go through and look for reasonable defaults for things.
    19 * order/order.php page should be created too, this gives simple overview of order in which things should be done when they are not required.
    2023* ~~Add a boolean to the flights table so it can be marked as a boresite, for sorting purposes.~~
    2124* ~~Add a blocked text field to flight status so that a message can be recorded when a status is marked as blocked.~~
    22 
    23 * See if progress view / ~~order view is necessary~~.
    24 * Determine search stuff properly. Do once progress view is sorted, probably use get variables.
    25 * Make objects for things like PIs, Flights etc...
    26 
    2725
    2826