----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "engine-devel" <engine-devel@ovirt.org>, "infra" <infra@ovirt.org> Cc: "Eli Mesika" <emesika@redhat.com> Sent: Sunday, March 2, 2014 12:39:16 PM Subject: [ATN] ovirt-engine dbscritps cleanup (master)
Hello All,
The dbscripts of ovirt-engine master were cleaned up, to match other scripts in tree.
Developer visible changes are:
1. Removal of create_schema.sh, upgrade.sh, cleandb.sh, refreshStoredProcedures.sh in favour of single schema.sh script, note the -c parameter.
Usage: ./schema.sh [options]
-h - This help text. -v - Turn on verbosity (WARNING: lots of output) -l LOGFILE - The logfile for capturing output (def. ) -s HOST - The database servername for the database (def. localhost) -p PORT - The database port for the database (def. 5432) -u USER - The username for the database (def. engine) -d DATABASE - The database name (def. engine) -m MD5FILE - Where to store schema MD5 files (def. ) -c COMMAND - Command: apply|refresh|drop -t - Force cleaning tasks and compensation info.
2. Introduction of schema-dev.sh as a wrapper to schema.sh with defaults as a utility for developers.
- always enable md5. - always enable logging. - apply command as default.
you should use this for create new DB or upgrade the existing one with the same call Example : ./schema-dev.sh -u engine -d engine This will create the engine DB if not exists and upgrade the DB if engine database exists
3. Shell upgrade script is not receives entire settings via DBFUNC_* environment variables.
Regards, Alon Bar-Lev