-
-
Notifications
You must be signed in to change notification settings - Fork 45
Open
Labels
databaseSomething to address on a database levelSomething to address on a database levelenhancementNew feature or requestNew feature or requestproposalWe want to discuss this to decide if it should be implementedWe want to discuss this to decide if it should be implemented
Description
The current design of data_processed has a primary key on did, evaluation_id, so one particular row is updated every time a dataset is attempted to be processed. In particular, the num_tries records the history.
mysql> DESCRIBE data_processed;
+----------------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+----------------------+--------------+------+-----+---------+-------+
| did | int unsigned | NO | PRI | NULL | |
| evaluation_engine_id | int | NO | PRI | NULL | |
| user_id | int | NO | | NULL | |
| processing_date | datetime | NO | | NULL | |
| error | text | YES | | NULL | |
| warning | text | YES | | NULL | |
| num_tries | int | NO | | 1 | |
+----------------------+--------------+------+-----+---------+-------+
I would rather record each processing attempt. The table would need a new primary key (a sequential identifier is fine), and num_tries then becomes derivative (count the matching (did, evaluation_id) rows). This would provide a history of the errors and when attempts have been made.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
databaseSomething to address on a database levelSomething to address on a database levelenhancementNew feature or requestNew feature or requestproposalWe want to discuss this to decide if it should be implementedWe want to discuss this to decide if it should be implemented