DBIx::C...re_sets(3)

✨ NAME ✨

This is the DBIx::C...re_sets(3) page from User Contributed Perl Documentation, and the full-name moment is DBIx::Class::Migration::Script::Help::fixture_sets — it's all about fixture sets to dump or load, bestie. 🎀

🌸 SYNOPSIS 🌸

dbic-migration dump --fixture_set roles --fixture_set core

💖 DESCRIPTION 💖

Okay so when you're dumping or populating fixture sets, you use this to set which sets. It's giving "pick your sets" and I'm obsessed. ✨

🫶 Aliases

• fixture_set — the alias. That's the name this option also answers to. 💅

🦋 Value

• Str or Array of String. Defaults to 'all_tables'.

Please note that if you manually describe your sets as in the above example, you don't automatically get the "all_tables" set. And that set is a fixture set of all database information — it is not the 'all' of the sets. Important distinction, bestie. 🫶

We automatically create the "all_tables" fixture set description file for you when you prepare a new migration of the schema. You can use this set for early testing, but I recommend you study DBIx::Class::Fixtures and learn the set configuration rules, and create limited fixture sets for given purposes, rather than just dump / populate everything, since that is likely to get big pretty fast. 🔥

My recommendation is to create a core 'seed' set, of default database values, such as role types, default users, lists of countries, etc. and then create a 'demo' or 'dev' set that contains extra information useful to populate a database so that you can run test cases and develop against. That's the vibe: seed first, demo/dev later. 🌈

👑 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.

💀 COPYRIGHT & LICENSE 💀

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

---

Bye bestie! 🫶 This page is from perl v5.42.0, dated 2020-06-03 — and the footer shortens it to DBIx::C...re_sets(3). Slay. 💖