moodle/backup/version.php

<?PHP  //$Id$
// This file defines the current version of the
// backup/restore code that is being used.  This can be
// compared against the values stored in the 
// database (backup_version) to determine whether upgrades should
// be performed (see db/backup_*.php)

$backup_version = 2006011600;   // The current version is a date (YYYYMMDDXX)

$backup_release = "1.6dev";  // User-friendly version number
Copied from old backup_version.php (to be more consistent with the rest of the modules) 2003-07-31 16:55:11 +00:00			`<?PHP //$Id$`
			`// This file defines the current version of the`
			`// backup/restore code that is being used. This can be`
			`// compared against the values stored in the`
			`// database (backup_version) to determine whether upgrades should`
			`// be performed (see db/backup_*.php)`

Part of Bug 4583. Now backup tables are moodle-style compliant. Also, the 4th parameter used in insert_record() has been erased to avoid the bug itself. PortgreSQL upgrade not tested! (http://moodle.org/bugs/bug.php?op=show&bugid=4583) 2006-01-16 10:23:48 +00:00			`$backup_version = 2006011600; // The current version is a date (YYYYMMDDXX)`
Copied from old backup_version.php (to be more consistent with the rest of the modules) 2003-07-31 16:55:11 +00:00
Part of Bug 4583. Now backup tables are moodle-style compliant. Also, the 4th parameter used in insert_record() has been erased to avoid the bug itself. PortgreSQL upgrade not tested! (http://moodle.org/bugs/bug.php?op=show&bugid=4583) 2006-01-16 10:23:48 +00:00			`$backup_release = "1.6dev"; // User-friendly version number`