- SEE ALSO
- COPYRIGHT & LICENSE
DBIx::Class::Migration::Script::Help::drop_tables - drop all tables to the connected database
dbic-migration drop_tables --schema_class MyApp::Schema
Drops all the tables in the connected database with no backup or recovery. For real! (Make sure you are not connected to Production, for example)
This command is intended to be a developer convenience function. It is not intended to be used as a general purpose administration tool.
This command accepts the following options. You may learn more about each option by typing
dbic-migration help OPTION. The following is a summary.
Adds the listed paths to @INC. Handy during development when you want to use a development schema class.
Accepts Str. Required.
This is the schema we use as the basis for creating, managing and running your deployments. This should be the full package namespace defining your subclass of DBIx::Class::Schema. For example
If the "schema_class" cannot be loaded, a hard exception will be thrown.
When using a
sandbox_class for generating developer level database sandboxes, you may wish to place the sandbox in a directory other than the default (which is under the
share directory off the project root).
Aliases: T, sb
Accepts: String (default: SqliteSandbox)
The class we use to create a developer level database sandbox.
Connection information to an already created and running instance of a database. If you don't specify this, we will assume you want a developer level sandbox ( See "sandbox_class" in DBIx::Class::Migration::Script).
See DBIx::Class::Migration for author information
See DBIx::Class::Migration for copyright and license information