Changes between Version 4 and Version 5 of statusdatabase

Timestamp:

Aug 11, 2014, 9:51:47 AM (11 years ago)

Author:

tec

Comment:

--

statusdatabase

@@ -1 @@
-== Structure of current ARSF Database ==
+== Structure of new ARSF Database ==
+
+'''Things to change in database revision 2'''
+* Move project_flights.area to flights.area ?
+* Move project_flights.priority to flights.priority ?
+* Remove sensor_status.id primary key and use the submit_time as primary key.
+
+
+
 
 The database is made up of 9 tables, joined together by relations. See below for a diagram of the database tables and relations
@@ -33 +41 @@
 ||  || data_recieved_on || Date ||  ||  ||
 
-
-
-
-
-
-
-
-
-
-
+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.
+||||||||||||= project_flights Table =||
+||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =||
+|| Primary Key || flight_id || Integer(4 Bytes) ||  Required  || Value must be in the flights table. ||
+|| Primary Key || project_code || Text (variable length) ||  Required  || Value must be in the projects table. ||
+||  || priority || Text (variable length) ||  Required  || Value must be in the priorities table. ||
+||  || area || Text (variable length) ||  Required  ||  ||