Details
Assignee
UnassignedUnassignedReporter
Matthew JonesMatthew JonesComponents
Affects versions
Priority
Minor
Details
Details
Assignee
Unassigned
UnassignedReporter
Matthew Jones
Matthew JonesComponents
Affects versions
Priority
Created February 28, 2017 at 8:51 AM
Updated August 30, 2017 at 9:54 AM
We had this bug come up that produced a log when the student went back to complete a partially completed evaluation.
Looking at the database for these ids
There were two rows that came up for the same user. My best guess is that someone hit save twice "really" fast as the times were almost identical. I feel like the fix might be to either disable the save button after clicking (a common fix in Sakai) or to have a constraint on group_id and evaluation, since it only allows one response per person currently.
We haven't seen this before, and the solution was just to remove one of these manually from the eval tables.