Log of /trunk/webwork2/bin/wwdb_addgw

---

Revision 5319 - (view) (download) (annotate) - [select for diffs]
Modified Mon Aug 13 22:59:59 2007 UTC (5 years, 9 months ago) by sh002i
File length: 11553 byte(s)
Diff to previous 3973

updated copyright dates

---

Revision 3973 - (view) (download) (annotate) - [selected]
Modified Wed Jan 25 23:13:56 2006 UTC (7 years, 3 months ago) by sh002i
File length: 11551 byte(s)
Diff to previous 3392

forward-port from rel-2-2-dev: (update copyright date range -- 2000-2006.
this is probably overkill, since there are some files that were created
after 2000 and some files that were last modified before 2006.)

---

Revision 3392 - (view) (download) (annotate) - [select for diffs]
Modified Wed Jul 20 18:28:55 2005 UTC (7 years, 10 months ago) by gage
File length: 11561 byte(s)
Diff to previous 3388 , to selected 3973

Fixed error that kept the script from working on courses whose
names contained an underscore.

Added `   ` around course names to handle courses whose names
have hyphens in them (and other weird characters)

Added print comments so that you see a running commentary of what
is being changed.  Once this script is debugged we might want
to turn these off.

---

Revision 3388 - (view) (download) (annotate) - [select for diffs]
Added Mon Jul 18 23:10:35 2005 UTC (7 years, 10 months ago) by glarose
File length: 11229 byte(s)
Diff to selected 3973

Add command-line utility to update sql and sql_single databases to include
gateway fields.  Use: wwdb_addgw [-h] [sql|sql_single]

Adds fields to the set and set_user tables in the WeBWorK mysql databases
that are required for the gateway module.  The script prompts for which
courses to modify.  Adding gateway database fields to existing courses
should have no effect on those courses, even if they are running under a
non-gateway aware version of the WeBWorK system.  (I haven't rigorously
tested this.)

If -h is supplied, the script hides the mysql password when it prompts for
it (this assumes that a Unix based stty -echo works).  If sql or sql_single
are supplied, they become the default database format.

Note that this has been tested, but not rigorously.  Please let me know
if you find that it does not perform as advertised.  It might be wise to
back up the database tables before using, and to check that it does what
we expect (that is, adds columns to the set and set_user tables) after
running it.