|Last updated||2003-02-03 13:14:42 EST|
|Doc Title||DLXS Database Upgrade Utility|
|Author 1||Blanco, Jose|
|CVS Revision||$Revision: 1.8 $|
dbmove is used to move a dlxs database from one type of database engine to another. Currently, it supports moving the dlxs database from CSV to MySQL, or from MySQL to CSV. At DLPS, we also use it to create a database for release to customers of dlxs.
If moving from the CSV database to MySQL, make sure that:
You can then issue the command
dbmove -s CSV -t MySQL
If moving from a MySQL database to CSV, make sure that there are no files in the $DLXSROOT/misc/db directory, and that the dbmove script has permissions to write to that directory. Since the MySQL database contains tables with potentially enormous amounts of data, like the sessions, and Pageview tables, the dbmove script will not permit you to move the entire MySQL database to CSV. You can use the "-r all" switch to indicate that only collmgr tables with userid dlxsadm, and production should be moved; and that nothing is moved from the PageviewFig, BookBagDB, and sessions tables. Certain sample ids from the Pageview table are moved. The command to issue is then:
dbmove -r all -s MySQL -t CSV
NOTE: This type of functionality is really only for DLPS. It is used to create the release CSV directory that becomes part of the DLXS deliverable. It will contain a sample of DLPS collections and groups with userid dlxsadm, and production (see discussion on collmgr for an explanation of these users). In order to execute this, you need to enter the following command:
dbmove -r [all | release | workshop ] -s MySQL -t CSV. The -r switch indicates that we only want to place rows in the CSV tables with userid dlxsadm, or production, and the values all, release, and workshop mean the following:
In addition to these collections, the CSV database created will contain a few sample ids in the Pageview table. The PageviewFig, BookBagDB, and sessions tables will be created, but will contain no data.