Loading a student roster

The only data you need to provide to ob2 is the student roster, which is stored in the users table. Here is the schema for that table (at the time of writing):

• id INT PRIMARY KEY
• name TEXT
• sid TEXT
• login TEXT
• github TEXT
• email TEXT
• super INT
• grouplimit INT
• photo BLOB

You need to acquire a student roster from your professor. It should contain 1) properly-capitalized full name, 2) student ID, and 3) email address. You should populate the other fields like this:

• id - Count up from 1. Do not use 0 as an id. We suggest sorting the students alphabetically by name before assigning id's, for ease of administration.
• name - Full name. Take this value from your roster.
• sid - Student ID. Take this value from your roster.
• login - Assign these starting from "aa", "ab", etc. To generate a list of logins, check out the useful python functions section of the Wiki. You can also set these to NULL if you are not using the instructional accounts feature.
• github - You must set these to NULL. Students will register with their own GitHub accounts. A NULL value in the github field means the student has not yet registered.
• email - Email address. Take this value from your roster.
• super - Set this to 0 for students. Set this to 1 for TA/Staff accounts. This field does not actually convey any special permissions. It is for statistics only. See Feature: Staff accounts for more information.
• grouplimit - This is the number of groups that a student can create or join, in addition to their existing groups. If you are not using the groups feature, set this to 0. CS162 sets this number to 1 for all students, because students can only be in one group. You can increase/decrease this number from the TA administration interface.
• photo - Set this to NULL. If you enable student photos, then students will be prompted to upload a photo of themselves when they register on the autograder. The photo is stored as a blob here.