Consider flipping `ConfigDB` from a single row to a hash table?
jadudm opened this issue · 0 comments
jadudm commented
We currently store the config as a single row. This is because we have a mechanism in the sqlitedb abstraction to do so.
We could flip this so that every config value is a key/value pair.
| config_flag | config_value |
|---|---|
| reset_cron | 0 0 * * * |
| minimum_minutes | 5 |
This way, if we change the values in the config file from one version to the next, we don't have to change the schema. This would eliminate a schema update issue, which we have not yet investigated/tackled.
There are other ways to handle this. Ultimately, the issue revolves around needing to maintain some config that might change as we update the software along side the API key, FCFS_Seq_id, and other user-entered information.