Telegram feature is in the code but not the logic to associate a channel to a comp.
As we would like to change db the least possible after release, I was thinking about the correct way to add it.
We could very simply add a column to Competition table, or we could add a table, named CompFeature, with columns comp_id, feature, value.
This way, if any new feature is added and turned on, we will have a new row for each feature and each competition, and probably we could reduce need of changing db in the future.
The same could be done for other object that we think could be helpful in the future, maybe task.
Telegram feature is in the code but not the logic to associate a channel to a comp. As we would like to change db the least possible after release, I was thinking about the correct way to add it. We could very simply add a column to Competition table, or we could add a table, named CompFeature, with columns comp_id, feature, value. This way, if any new feature is added and turned on, we will have a new row for each feature and each competition, and probably we could reduce need of changing db in the future. The same could be done for other object that we think could be helpful in the future, maybe task.
Thoughts?