WeBWorK 2.0, SQL course databases (using the "sql" database layout) are
each stored in their own SQL database. Therefore, the "SQL Admin User"
needs to have permission to create and delete databases (FILE) and
create and drop tables (CREATE, DROP), as well as the standard
read/write permissions of SELECT, INSERT, UPDATE, and DELETE.|
At Rochester, we typically use the "root" user as the "SQL Admin User",
but there is no reason why one couldn't create a separate user, as long
as it had the necessary privileges.
The upcoming WeBWorK 2.1 release will include support for a new
database layout, "sql_single", which stores the data for all courses
using that layout in a single database. This streamlines the course
creation/deletion process (since one no longer has to create or delete
a course database), makes database access more efficient, and reduces
the level of access needed to create and delete SQL courses.
There will be a utility for converting courses from the "sql" layout to the "sql_single" layout.
You may want to take a look at the Database Layout Manual, which clarifies some of the terminology we've been tossing around.
<| Post or View Comments |>