Advanced search
Log In
New Account
Home My Page Project Cloud Code Snippets Project Openings BRisa UPnP
Summary Forums Tracker Lists Tasks Docs News SCM Files BRisa website Wiki

Milestone #04 - Brisa 0.7: Browse Tasks | Gantt Chart | Download as CSV | Upload CSV

Submitted By:
André Dieb Martins (dieb)
Percent Complete:
Start Date:
End Date:
Task Summary:
Migrate configuration from txt file to database model
Original Comment:
Expected release version: python-brisa-0.7.1

Actual configuration on BRisa is done with python configuration API and the result is a single text-based configuration file. This will cause unwanted complexity when it comes to:
- Merging configurations (upgrade, downgrade)
- Watching configuration for runtime changes. For example, setting the usage of a plugin from OFF to ON on the configuration during runtime*

The proposed database model is composed by three tables
. db_object (id, name, type): holds all the objects and their types (for faster lookup);
- db_parameter (id, value): holds parameters, which are a key-value pair, but the key is stored on db_object as name;
- db_section (id): holds section id's. Section name is stored on db_object;
- db_parameter_db_section (param_id, section_id): holds relationship between parameters and sections (enables multiple parents for a parameter);

Since this task's code is much alike the filesystem-persistence code, the assignee should reuse the existing code , optimize it and submit the optimizations to the filesystem-persistence.

Database API for this task must be sqlite, since BRisa already depends on it.

* Watching these flags and constants is part of another task, it's here just for explaining purposes.
Assigned To
Dependent On Task

Tasks That Depend on This Task

Task Id Task Summary
825 Improve configuration tool

No Related Tracker Items Have Been Added

No Comments Have Been Added

No Changes Have Been Made

Terms of Use    Privacy Policy    Contribution Guidelines    Feedback

Powered By GForge Collaborative Development Environment