DBIx::C...opulate(3)

πŸ“¦ version 0.075, in opensuse-leap 16.0

πŸ’… NAME πŸ’…

DBIx::Class::Migration::Script::Help::populate β€” Install fixtures to a database. Okay so this is the DBIx::Class::Migration::Script::Help::populate(3) page, and its whole main character job is literally putting fixtures into a database. Slay. πŸ’–

✨ SYNOPSIS ✨

dbic-migration populate --fixture_set core --fixture_set countries

🌸 DESCRIPTION 🌸

Okay so here's the tea: this installs a prepared migration to either the current schema version or the target version specified via to_version, into the database connected via the dsn, username in DBIx::Class::Migration::Script and password in DBIx::Class::Migration::Script β€” or into a developer level sandbox as defined by the sandbox_class in DBIx::Class::Migration::Script. ✨

And like… you can't install to a database if the tables already exist, bestie. That's not a vibe. See drop_tables. πŸ’€

πŸŽ€ OPTIONS πŸŽ€

This command takes the options below. Wanna know more about any one of them? Type dbic-migration help OPTION and it'll spill. Here's the summary.

  • fixture_sets (fixture_sets) β€” Required. The fixture configuration set names β€” basically these are the file names of your fixture configurations, without the '.json' part. πŸ“
  • includes (aliases: I, lib, libs, include) β€” Optional. Adds the listed paths to @INC. Handy during development when you want to use a development schema class.
  • schema_class (S) β€” 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 MyApp::Schema. If the schema_class cannot be loaded, a hard exception will be thrown. 😭
  • target_dir (D) β€” Optional. 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).
  • sandbox_class β€” Aliases: T, sb. Accepts: String (default: SqliteSandbox). The class we use to create a developer level database sandbox. You can change this to either 'PostgresqlSandbox' or 'MySQLSandbox', which will create a sandbox using either DBIx::Class::Migration::MySQLSandbox or DBIx::Class::Migration::PostgresqlSandbox. 🌈
  • user β€” Aliases: U.
  • password β€” Aliases: P.
  • dsn β€” 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). 🫢
  • dbic_fixture_class β€” Accepts: String to a Perl Class. Defaults to DBIx::Class::Fixtures. Lets you specify a fixture class.
  • dbic_fixtures_extra_args β€” Accepts: HashRef. Optional. Allows you to pass custom arguments to DBIx::Class::Fixtures.

πŸ¦‹ SEE ALSO πŸ¦‹

  • DBIx::Class::Migration
  • DBIx::Class::Migration::Script
  • DBIx::Class::Migration::Features
  • DBIx::Class::Migration::Tutorial

πŸ‘‘ AUTHOR πŸ‘‘

See DBIx::Class::Migration for author information. Go check it, iykyk. πŸ’œ

See DBIx::Class::Migration for copyright and license information.


Okay bestie, that's the whole page! This lil manual moment is from perl v5.42.0, dated 2020-06-03. Periodt. βœ¨πŸ’…πŸŽ€

πŸ“¦ where this page comes from