35 | | |
36 | | |
37 | | |
38 | | |
39 | | |
40 | | |
41 | | |
42 | | |
43 | | |
44 | | |
| 43 | 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. |
| 44 | ||||||||||||= project_flights Table =|| |
| 45 | ||= Key =||= Field Name =||= Value Type =||= Constraints =||= Notes =|| |
| 46 | || Primary Key || flight_id || Integer(4 Bytes) || Required || Value must be in the flights table. || |
| 47 | || Primary Key || project_code || Text (variable length) || Required || Value must be in the projects table. || |
| 48 | || || priority || Text (variable length) || Required || Value must be in the priorities table. || |
| 49 | || || area || Text (variable length) || Required || || |