veaceslav / tumorprofil Goto Github PK

Currently I see the following groups of users:
Read only pathology data, no access to disease history
Read only pathology data, read only disease history
Read and write pathology data, read only history
Read only pathology data, read and write history
Read and write everything.
(pathology data corresponds to the main window, editing happens through "Befunde eingeben" button or through the delegate in the table view. Disease history refers to the window which opens from the "Krankheitsverlauf" button)

1. First question is where to define the role for a user: Either by adjusting read/write permissions for tables on the db level. Or by setting flags / roles in the tumorusers table.
   Normally, the first option is the natural one, but I am not sure if it is easy to detect the read/write permissions at run time, which would be needed because:

2. It would be nice to reflect in the UI the available rights.
   no write permission on pathology data -> button is greyed, delegate does not offer editing
   no read permission on disease history -> button is greyed, window does not open
   no write permission on disease history -> widgets are not editable

(At some places there may already be preliminary code in the UI which intends to support such modes)

Allow to store a configuration file alongside the binary which gives the database connection parameters except for username / password.
If such a file is found, the relevant settings are used and cannot be changed.
The values read from the file should not be stored locally, instead always read from the file.
Location of the file should be in the same directory as the binary that is run.

With an available db connection (like from a master config file in the previous issue), start up to go straight to a username / password enter dialog.
Username can be stored locally for convenience. Password shall not be stored for now (must be reentered each time)

Running the application with no MariaDB server (neither on the local machine, nor any configured remote) gives an error (Failed to create tables) and quits.
Should

1. check if there is a connection at all
2. if not, go straight to the config dialog

(or how should I enter the config dialog?)

When running the conversion script, only one single PathologyProperty entry for each Pathology is entered into the database.
I did not check if the other ...Properties tables work correctly; there's usually only a single entry at the moment.

Allow to change the current user's db system password from the TumorProfil app.