Klever

Vladimir Gratinskiy wrote:

Now for uploaded jobs I have to show start and finish decision dates. Earlier it was missed (all jobs on ldvstore). To show this data I need to save it to archive and then, after job uploading, to DB. There is model "SolvingProgress" where these dates are saved. But for creating model I need also other fields that can't be null. So all fields for this model are saved in "progress". It is:
[priority, scheduler, start_date, finish_date, tasks_total, tasks_pending, tasks_processing, tasks_finished, tasks_error, tasks_cancelled, solutions, error, configuration]

I understand that this isn't a bug but a minor refactoring. It looks like a bit incorrect design, if you need to transfer useless data in such the way. Perhaps you can split data and corresponding models so that just really necessary values will be downloaded/uploaded without model requirements. Moreover, it should allow to avoid duplicates. For instance, it seems that the same configuration is stored for progress and in directory "Configurations".

Does this problem still exist?

It exists, but I do not think that it is important at all.