Fixing the 1.9 code will remedy this problem only for the specific case, but adjusting the 2.x code will prevent bad data insertion regardless of the cause/source.

We just encountered this issue as well; the symptoms are well-reported in MDL-29877 which I think this issue will resolve. We can reproduce it on demand with a 1.9 site and verified that this patch resolves the issue.

Added Andrew Davis as a watcher since he looked at MDL-37672. I suppose this is more of a backup/restore issue but it does affect the gradebook.

Hi. I've put this in to the next stable team sprint. Sorry to keep you waiting.

No worries.

Adding some testing instructions and putting this up for peer review. The proposed code change looks fine.

I did try to set Fred Woolard as the issue assignee but wasn't able to. I'm guessing there is some tracker permission involved there.

Thanks Fred and Andrew,

Patch looks good, it will be nice if you could attach 1.9 backup file to make testing easy.
Also, comment at #L0R153 doesn't comply with moodle coding standards.

[y] Syntax
[y] Output
[y] Whitespace
[-] Language
[-] Databases
[-] Testing
[-] Security
[y] Documentation - comment at #L0R153
[y] Git
[y] Sanity check

Attached a generalized backup. Verified that it crashes current master.

I don't have a 1.9 backup to hand. If anyone has one please attach it. I'll see what I can dig up. EDIT: there is one attached.

Regarding the comments, the new comment is in line with style used throughout that file. I've raised MDL-38860 to go through fix them all in one go.

Putting this up for integration.

The main moodle.git repository has just been updated with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week.

TIA and ciao

Hi,

Sorry another minor coding style thing here, the NULL should be lowercase:
http://docs.moodle.org/dev/Coding_style#Booleans_and_the_null_value

I've decided i'll fix this up myself in order to keep things moving.

I take it all back! I notice from the surrounding code its using NULL all over.

Sorry - I agree with your call to use the same style as the surrounding code.

Integrated to master, 24 and 23. thanks Fred/Andrew!

Sorry for the mixed messages about coding style - it'd good to stick to the coding style and eventually over time we'll hopefully end up with a consistent coding style, but it makes sense to make the style look good with the surounding code.

Dan, sorry for the delay. Rebased each of the branches.

Tested on the 2.2, 2.3, 2.4 and master branches.
Everything seemed to work okay.
No errors encountered.
Test passed.

Your awesome contributions are now part of Moodle, your fav LMS out there.

Closing this as fixed.

Many thanks for all the hard work, ciao