Configuration storage
matthiasrigaud opened this issue · 5 comments
Define an architecture for DB, integrate DB to project, implement functions relative to DB
should have wrote it here a long time ago but well..
so for the database architecture :
each config is either a table or a view
setters type of configs are tables with one settings in each row,
includes type of configs are view made of other setters config tables
- a table which link config id to the right table/view name
- each table/view contains :
- an id (not really relevant here since the setting name is unique in a config therefor the name is the id)
- a name (unique to the configuration)
- and a value of type blob (binary large object)
Database is almost ready to be integrated to the service, most of it can already be integrated (create/delete config, set/delete setting).
I'm not sure about the load_config in the protocol ? should it ask for the database to fetch all settings of a the specified config and return them ?
Need more work on the views, its seems doable but rather complicated, merging multiple tables between them is possible with statement such as union or join. however the tricky part is to select for each row, a column either from one table or another upon some conditions, so I need to find an answer for that.
@Riz-cros I think it's not important to think to "load_config" now, and I'm not sure you'll have to do something during the configuration loading anyway. This request is made for the library, to allow it to inform the service of its presence, and to specify the key and the type of "connection" (RO/RW).
Remettre au propre la DB
Cacher le load des configs