CPAN::Groonga

 DBIx::Class::Migration;

our $VERSION = "0.075";
$VERSION = eval $VERSION;

use Moo;
use JSON::MaybeXS qw(JSON);
use File::Copy 'cp';
use File::Spec::Functions 'catdir', 'catfile', 'updir';
use File:

  class=> $_,
    quantity => "all",
  } } @_;
}

sub _create_all_fixture_config_from_sources {
  JSON->new->pretty(1)->encode({
    "belongs_to" => { "fetch" => 0 },
    "has_many" => { "fetch" => 0 

s = $self->_filter_views(@sources);
  my $all_tables_path = catfile($fixture_conf_dir,'all_tables.json');
  _create_all_fixture_set($all_tables_path, @real_tables);

  if(my $previous = _has_previous_

e::Spec::Functions 'catdir', 'catfile';
use JSON::MaybeXS;

requires 'schema';

sub populate {
  my ($self, @sets) = @_;

  my $fixtures_init_args =
    JSON::MaybeXS->new->decode( $ENV{DBIC_MIGRATION

BIx::Class::Fixtures> to populate
them to the current database.

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

=head2 set_has_fixtures

Requires $arg

Given a set name, returns a boolean about if

have the following:

    /share
      /fixtures
        /1
          /conf
            all_tables.json
      /migrations
        /_source  (There's stuff in here, but we won't peek!)
        /SQLite
 

rve.  In any case you
can take a quick peek to get the idea:

C</share/fixtures/1/conf/all_tables.json>

    {
       "sets" : [
          {
             "quantity" : "all",
             "class" : "Cd

     },
       "has_many" : {
          "fetch" : 0
       }
    }

L<DBIx::Class::Fixtures> uses JSON for its configuration.  In this case you
can note that we are just dumping all the rows in all th

/fixtures
        /1
          (Same as before)
        /2
          /conf
            all_tables.json
      /migrations
        /_common
          (Same as before)
        /_source
          (system 

base-schema.db

Ok, we got a bunch more files.  You can see that we've created a new
C<all_tables.json> fixture configuration, which if you peek inside, you will
see has been updated to include your n

      (Same as before)
        /2
          /conf
            all_tables.json

By default we build you a fresh C<all_tables.json> that should reflect any new
or removed tables.  Additionally, if there

ation set names (basically these are the file
names of your fixture configurations, without the '.json' part.

=head2 includes (I,lib,libs,include)

Optional.

Adds the listed paths to @INC.  Handy du

ation set names (basically these are the file
names of your fixture configurations, without the '.json' part.

=head2 includes (I,lib,libs,include)

Optional.

Adds the listed paths to @INC.  Handy du

ation set names (basically these are the file
names of your fixture configurations, without the '.json' part.

=head2 includes (I,lib,libs,include)

Optional.

Adds the listed paths to @INC.  Handy du

dir', 'catfile';
use File::Path 'mkpath';
use JSON::MaybeXS;

requires 'schema';

sub dump {
  my ($self, @sets) = @_;

  my $fixtures_init_args =
    JSON::MaybeXS->new->decode( $ENV{DBIC_MIGRATION_F

 => $self->schema,
    configs => [map { "$_.json" } @sets],
    directory_template => sub {
      my ($fixture, $params, $set) = @_;
      $set =~s/\.json//;
      my $fixture_conf_dir = catdir($ENV{

<DBIx::Class::Fixtures> to dump
them from the current database.

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

=head1 SEE ALSO

L<DBIx::Class::Migration>, L<DBIx::Class::Migration::RunScript>

=h

ll also generate diffs and copy any fixture
configs etc (as well as generating a fresh 'all_table.json' fixture config). For
safety reasons, we never overwrite any fixture configs (even if
C<overwrite

ation set names (basically these are the file
names of your fixture configurations, without the '.json' part.

=head2 includes (I,lib,libs,include)

Optional.

Adds the listed paths to @INC.  Handy du

     /2
          (Same as before)
        /3
          /conf
            all_tables.json
            countries.json
      /migrations
        /_common
          (Same as before)
        /_source
    

otice that C<prepare>
made a fresh C<all_tables.json> for you, which has added your new bridge table
and it also copied over your custom C<countries.json> from the previous version.
Please note that t