Changes between Version 27 and Version 28 of ippToPsps_Database
- Timestamp:
- Apr 10, 2012, 1:11:35 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ippToPsps_Database
v27 v28 112 112 === The {{{pending}}} table === 113 113 114 the {{{pending}}} table is first populated by {{{queue.py}}} then read by instances {{{loader.py}}}. It consists of unique stage_ids for each batch type that has been queues for each box on the sky, as shown here: 114 115 116 {{{ 117 +--------+------------+----------+ 118 | box_id | batch_type | stage_id | 119 +--------+------------+----------+ 120 | 44579 | OB | 93141 | 121 | 44579 | OB | 93142 | 122 | 44579 | OB | 93143 | 123 | 44579 | OB | 93144 | 124 | 44579 | OB | 93145 | 125 | 44579 | OB | 93146 | 126 | 44579 | OB | 93147 | 127 | 44579 | OB | 93148 | 128 | 44579 | OB | 93149 | 129 | 44579 | OB | 93150 | 130 | 44579 | OB | 93151 | 131 | 44579 | OB | 93152 | 132 | 44579 | OB | 93153 | 133 etc 134 }}} 135 136 A foreign key constraint on {{{box_id}}} with the {{{box}}} table means that entries will be deleted automatically if a box definition is removed from the {{{box}}} table. 115 137 138 Also, {{{loader.py}}} instances will remove rows from this table as they begin to process them. If they fail to process the item in question for whatever reason, it will be re-queued the next time {{{queue.py}}} is run. 116 139 == The batch tables == 117 140 === The {{{batch}}} table ===
