SQL: is it the right tool for the job ? about cgru HOT 3 CLOSED

There is one advantage using SQL. All deleted jobs stored in statistics tables. And users can write various queries to get farm load statistics. This tools are not dealing with afserver at all. There is already one tool - web visor.
But!

1. Writing some deleted jobs data is a separate process. And there is no matter how active jobs are stored, within SQL or not. So server can store only deleted jobs in SQL.
2. There are such tiny SQL engines as SQLite, all database is in application library and does not needed to be installed - may be this is a simple solution. There can be an option to use internal or external database.
3. I think that it is normal for afanasy to have some own "database" engine, as it is simple, all SQL power does not needed, of course. And there is a great advantage in this case that we do not need to install and setup postgresql.

ps
Job has a description attribute, that is not used by afanasy system. But it is stored. Users can give informative values for it. For example departmentA.projectB.sceneC.shotD. And later perform interesting queries to statistics table. That is why i do not want to drop SQL at all. And if server can't connect to SQL database, it simple will not store any statistics (also it can be compiled to not use SQL at all).

from cgru.

In CGRU 2.0 everything will be stored in json files (folders structure).
SQL will be used for statistics only.

from cgru.

Done.

from cgru.