Changes between Version 15 and Version 16 of statusdatabase


Ignore:
Timestamp:
Aug 13, 2014, 10:50:04 AM (10 years ago)
Author:
tec
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • statusdatabase

    v15 v16  
    22
    33'''Things to change in database revision 2'''
    4 * Move project_flights.area to flights.area
    5 * Move project_flights.priority to flights.priority ?
     4* ~~Move project_flights.area to flights.area~~
     5* ~~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?
     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~~
    1010* Make sensor_status.username nullable? check data first
    1111* Go through and look for reasonable defaults for things.
    1212* 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.
    13 * Add a boolean to the flights table so it can be marked as a boresite, for sorting purposes.
    14 * Add a blocked text field to flight status so that a message can be recorded when a status is marked as blocked.
     13* ~~Add a boolean to the flights table so it can be marked as a boresite, for sorting purposes.~~
     14* ~~Add a blocked text field to flight status so that a message can be recorded when a status is marked as blocked.~~
    1515
    16 * See if progress view / order view is necessary.
     16* See if progress view / ~~order view is necessary~~.
    1717* Determine search stuff properly. Do once progress view is sorted, probably use get variables.
    1818* Make objects for things like PIs, Flights etc...