Save the execution parameters in the database

To save the paramters in a table, we have two options:

{
    "DB_NAME": { "2024-06-25T14:35:10Z": "my_db" }, 
    "DROP_DB": { "2024-06-25T14:35:10Z": "False" }
    ...
}

{ 
    "2024-06-25T14:35:10Z": { "DB_NAME": "my_db" }, 
    "2024-06-25T14:35:10Z": { "DROP_DB": "False" }

But in fact, there are two problems with the above representation:

If there are many paramters to save, it may take some time, and this would change the key (the time), which is not a good thing;
It would also duplicate the date as many times as there are parameters to save from the current execution.

Instead, I think we need to model Executions as follows:

{ 
    "identifier": "123",
    "createdAt": "2024-06-25T14:35:10Z",
    "parameters": {
        "DB_NAME": "my_db",
        "drop_db": "True",
        ...
    }, 
    "analysis": {
        "Patients": { "identifier": { "nb_empty_values": "0 }, ...}, 
        ....
    }
}

Nelly-Barret / BETTER-fairificator

Save the execution parameters in the database #79