- SEE ALSO
- COPYRIGHT & LICENSE
DBIx::Class::Migration::Script::Help::delete_table_rows - trunate existing tables
dbic-migration delete_table_rows --schema_class MyApp::Schema
delete on each table in the database, which clears out all your data but preserves tables. For Real! You might want this if you need to load and unload fixture sets during testing, or perhaps to get rid of data that accumulated in the database while running an app in development, before dumping fixtures.
If your table has a lot of rows, this command could take a long time to run depending on your database type.
Skips the table
dbix_class_deploymenthandler_versions, so you don't lose deployment info (this is different from
drop_tables which does delete it.)
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").
See DBIx::Class::Migration for author information
See DBIx::Class::Migration for copyright and license information