Changes between Version 26 and Version 27 of statusdatabase


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

--

Legend:

Unmodified
Added
Removed
Modified
  • statusdatabase

    v26 v27  
    55* need trigger for when last status is gone clear up flight sensors table.
    66* 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* Determine search stuff properly. Do once progress view is sorted, probably use get variables.
     8* Make objects for things like PIs, Flights etc...
    79* ~~priorities and progress tables, make fields unique?~~
    810* ~~Remove sensor_status.id primary key and use the submit_time as primary key.~~
     
    1012* ~~Go through and look for reasonable defaults for things.~~
    1113* ~~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...
    1414* ~~make flights ondelete cascade.~~
    1515* ~~make sensor_status delete cascade from flight sensor id~~