Implement database manager #4

Open
opened 2020-11-28 11:50:22 +03:00 by dkanus · 2 comments
Owner

We need a handler for the database messages, that will manage local databases and perform operations on them, based on received messages.

It needs to have it's own config file, where it lists:

  1. How often must database be saved on the disk (while it is loaded in memory);
  2. Where it is stored;
  3. Where/how often backup copies are stored. How much to store at once.

It must provide following commands:

  1. Create/remove/exists check for database's groups;
  2. Create/remove/exists check for files inside database;
  3. Create/remove/exists check for values in side files;
  4. Set/Get commands for values in files that overwrite them;
  5. Aside from a simple set of commands, we will need to support a number of value-changing commands such as add to int/float, add(append) value to JSON object/array.

These names do not have to be preserved, but they have to be documented.

It also must implement and document a number of response messages that report the result: success/failure (different type of failure per reason?).

Adding more is possible if deemed necessary during the implementation.

We need a handler for the database messages, that will manage local databases and perform operations on them, based on received messages. It needs to have it's own config file, where it lists: 1. How often must database be saved on the disk (while it is loaded in memory); 2. Where it is stored; 3. Where/how often backup copies are stored. How much to store at once. It must provide following commands: 1. Create/remove/exists check for database's groups; 2. Create/remove/exists check for files inside database; 3. Create/remove/exists check for values in side files; 4. Set/Get commands for values in files that overwrite them; 5. Aside from a simple set of commands, we will need to support a number of value-changing commands such as add to int/float, add(append) value to JSON object/array. These names do not have to be preserved, but they have to be documented. It also must implement and document a number of response messages that report the result: success/failure (different type of failure per reason?). Adding more is possible if deemed necessary during the implementation.
dkanus added the
enhancement
label 2020-11-28 11:50:22 +03:00
dkanus added this to the alpha1 milestone 2020-11-28 11:57:26 +03:00
Ggg_123 added the
question
label 2020-11-28 14:29:49 +03:00
Collaborator

Do we even need several DBs?

Do we even need several DBs?
Author
Owner

Corrected text a little, removed requirement for multiple databases.

Corrected text a little, removed requirement for multiple databases.
dkanus self-assigned this 2020-11-29 00:11:13 +03:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: dkanus/Avarice#4
No description provided.