...
If you are currently using demo data that you set up under Scheduler v3.1.1, and you want to continue using your current data, apply the following list of update.sql files:
update.sql (3.2.0)
update.sql (3.3.0)
update.sql (3.5.0)
update.sql (3.6.0)
update.sql (3.7.2)
update.sql (4.2.0)
To apply each update.sql, install all the distributed update.sql files to the folder /var/tmp/. Then run the following command for each update.sql in the order provided:
...
If you are updating from Scheduler v3.7.2 then apply only the latest (4.2.0) update.sql from the above list and then run the Update User Salt program below.
Update User
...
Salt
Configure and run the standalone: updateUserSalt, to convert DB user salt fields to new MIME flavored salts
...
Run the following SQL scripts:
This file contains the basic database schema and table structure for the Scheduler application. There is no data in this file and it must be used in conjunction with seed data in order to have a running application. The structure is based on Scheduler v4.1.0.
- Install the distributed demo-structure.sql file to /var/tmp/demo-structure.sql
demo-seed.sql
This file contains all the static data required by the application (e.g dropdown options, list of users, states, countries, etc).
...
| Code Block |
|---|
root@shell> mysql scheduler < /var/tmp/demo-data.sql root@shell> mysql scheduler < /var/tmp/demo-seed.sql |
demo-data.sql
This file contains a set of data for demonstration purposes. This includes demo templates, scheduled appointments, and more. Upon running this script (along with the populate-fake-subjects executable, and update.sql that follow) you should have all the data that you need to evaluate the application.
...
b. Windows
fakeSubjects.cmd <max-subject-id>
Finally, apply update.sql, and you will be all set.
...