*_has_changed logic is now useless

[veluca93]

Is there any reason to keep the {whatever}_has_changed logic in the loaders? We initially added it because we wanted to support loading only a subset of the tasks in a given contest, but now we can import tasks one-by-one: it seems to me that now it may cause more issues than those it solves (ie. none).

[stefano-maggiolo]

I think you folks are those with more experience in the loaders. Having said that, I believe that the idea was also to modify a task when it already had submissions attached to it.

[wil93]

For most use cases, there is no need to update the task:

• To update testcases, I can create a new dataset with cmsImportDataset
• To update the task statement, I can use cmsAddStatement -o

There are some use cases that I do with AWS like changing the time limit, or the task title, and maybe it would make sense to have some way of doing that with a script, but maybe it's not big enough of a reason to complicate the loaders...

[veluca93]

I can't find a use case in which I want to update eg. a time limit, doing it by AWS wouldn't be convenient and I couldn't just use cmsImportDataset though....