|<B>--printB>||Rather than actually running the database create/update/drop commands, Prints the commands to standard output|
|<B>--create-databaseB>||Send a CREATE DATABASE command. Note that <B>--setupB>, below, will automatically send a CREATE DATABASE if it needs one. This option is useful if you wish to create the database without creating any tables in it.|
|<B>--drop-databaseB>||Send a DROP DATABASE command. Use this in conjunction with <B>--setupB> to wipe and re-install the database.|
|<B>--setupB>||Actually set up your apps tables. This creates the database if need be, and runs any commands needed to bring the tables up to date; these may include CREATE TABLE or ALTER TABLE commands. This option is assumed if the database does not exist, or the database version is not the same as the applications version.|
|<B>--ignore-reserved-wordsB>||Ignore any SQL reserved words used in table or column definitions, if this option is not used and a reserved word is found it will cause an error.|
|<B>--no-bootstrapB>||dont run Bootstrap, mostly to get rid of creating initial data|
|<B>--helpB>||Print a brief help message and exits.|
|<B>--manB>||Prints the manual page and exits.|
Looks for all model classes of your Jifty application and generates SQL statements to create or update database tables for all of the models. It either prints the SQL to standard output (<B>--printB>) or actually issues the CREATE TABLE or ALTER TABLE statements on Jiftys database.
(Note that even if you are just displaying the SQL, you need to have correctly configured your Jifty database in ProjectRoot/etc/config.yml, because the SQL generated may depend on the database type.)
By default checks for SQL reserved words in your table names and column definitions, throwing an error if any are found.
If you want to permanently turn this behaviour off you can set CheckSchema to 0 in the database section of your applications config file.
Due to limitations of DBIx::DBSchema, this probably only works with PostgreSQL, MySQL and SQLite.
It is possible that some of this functionality should be rolled into Jifty::DBI::SchemaGenerator
Prints a help message if the users want it. If not, goes about its business.
Sets up the environment, checks current database state, creates or deletes a database as necessary and then creates or updates your models schema.
Take the actions we need in order to bring an existing database up to current.
Sets up a minimal Jifty environment.
Returns a Jifty::Schema object.
Probes our database to see if it exists and is up to date.
Create all tables for this applications models. Generally, this happens on installation.
Given a list of items that are the scalar names of subclasses of Jifty::Record, either prints SQL or creates all those models in your database.
Upgrade Jiftys internal tables.
Upgrade the applications tables.
Upgrade the tables for each plugin.
Given a BASECLASS to upgrade, and two version objects, FROM and TO, performs the needed transforms to the database. UPGRADECLASS, if not specified, defaults to BASECLASS::Upgrade
If the user wants the database created, creates the database. If the user wants the old database deleted, does that too. Exits with a return value of 1 if the database drop or create fails.
|perl v5.20.3||JIFTY::SCRIPT::SCHEMA (3)||2011-02-10|