Just hit this again.

Please fix.

Please, please, please!

If you add a new table, save the XML file, then reload the XML file, you can add a field.

"I think the problem is with multiple broswer tabs. For example, if you go and look at the definition to another field to see what type it is. That then causes an error when you save the one you are working on."

review the flow of that info... it shouldn't rely on session at all.

I've been trying to reproduce this in all ways possible:

• Create table, then field, back without saving
• Create table, then field, save (both without modifying the default "changeme" names and modifying them)
• Create and then, while editing the new field, in other tab (same session), look another exiting field specs (edit it, both saving and without saving)
• Force multiple "new field" executions to see if something is being reused incorrectly

And I haven't been able to get any error like the described above. So I'm going to close this as cannot reproduce. Please, if you find some sequence causing it... reopen and comment!

Slightly offtopic: Some days ago, I discovered that Moodle 2.0 sessions weren't being closed properly (due to one error in the destructor)... perhaps that could be causing some malfunction in session data, specially affecting the XMLDB editor when using more that one tab/window. Just a thought, not sure.

Ciao

Name: requirestudentdeclaration
Comment: Force the student to check a box following a statement about the work, e.g. not having plagiarized.
Type: int
Length: 2
Not null: not null
Default: 0

However, I was able to add a different field to mod/assignment/db/assignment_submissions.