DBIx::C...opulate(3)

💖 NAME 💖

Ok so this is the manual page for DBIx::Class::Migration::RunScript::Trait::Populate — Populate fixtures — and it shows up as DBIx::C...opulate(3) in the header. It's part of User Contributed Perl Documentation. Also, the original NAME block has a literal =head1 SYNOPSIS sitting right there — formatting chaos, but we're keeping every detail, bestie. 💖

---

🫶 SYNOPSIS 🫶

use DBIx::Class::Migration::RunScript;

builder {
  'SchemaLoader',
  'Populate',
  sub {
    shift->populate('countries');
  };
};

That's the whole vibe: SchemaLoader, then Populate, then a sub calling populate('countries'). Slay. 💅

🌸 DESCRIPTION 🌸

This is a Moo::Role that adds a populate method to your run script. The way that works is it lets you access any of your previously dumped fixtures. You might find this useful when installing a database that was previously setup.

This trait requires a "schema" previously defined, such as provided by DBIx::Class::Migration::RunScript::Trait::SchemaLoader.

🎀 Tiny but important: no schema, no populate party. Get that schema sorted first.

💅 methods 💅

This class defines the follow methods. (Yes, "follow" — we're keeping the original's exact wording, no cap.)

🦋 populate 🦋

Requires $arg || @args.

Given a fixture set (or list of sets), use DBIx::Class::Fixtures to populate them to the current database.

When naming sets, you skip the '.json' extension.

🍓 set_has_fixtures 🍓

Requires $arg.

Given a set name, returns a boolean about if that set actually has fixtures previously dumped.

🌈 SEE ALSO 🌈

DBIx::Class::Migration, DBIx::Class::Migration::RunScript

👑 AUTHOR 👑

See DBIx::Class::Migration for author information.

💜 COPYRIGHT & LICENSE 💜

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

---

okay that's the whole page, bestie 💖✨🦋 This was <pink>DBIx::C...opulate(3)</pink> from the User Contributed Perl Documentation crew — footer vibes: perl v5.42.0, dated 2020-06-03. Periodt. 🎀💅