databases/p5-DBIx-Class-Fixtures from 1.001013nb3 to 1.001018.
pkgsrc changes:
- adjust dependencies
Upstream changes:
1.001018
- Reduced the size of a PK in the fixtures to stop (hopefully) some occasional
error reports
1.001017
- POD fixes (justin hunter++)
- Changed the test suite so it doesn't mindlessly break with the changes
introduced by DBIC 0.08200 (nerox++ for bug report).
1.001016
- Support more Postgresql types for datetime_relative (added TIME, DATE,
INTERVAL, TIMESTAMP)
- If $result_source->column_info defines a sequence, make sure we properly
set that sequence to whatever the max value currently is.
1.001015
- ::External::File makes the path if its missing
1.001014
- Allow you to perform value substitutions inside config-sets
- Added a framework to allow you to backup / restore data external to the
database as part of your fixtures. Added an external handler for File
based data, and docs and tests for this.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Changes from previous:
1.001013
- fixed functionality in last release by more deeply cloning parameters, which
prevents bad things when parameters get deleted in the wrong places. Also
be sure we clear state properly after a dump.
1.001012
- Added new method 'available_config_sets' which returns and caches a list of
all the json set configs found in the 'config_dir' directory. This was added
to make it easier when you need to dump all the fixtures programatically.
- Added method 'dump_config_sets' to let you dump more than one set at a time
more easily
- Added method 'dump_all_config_sets' which helps automate dumping all your
current config sets to a directory.
1.001011
- Added an excludes resultsource option to the ->dump({all=>1,...}) feature
- Allow you to directly set a configuration via a Perl HashRef instead of a
JSON file. Useful for testing and when you have simple or generated configs.
- New option to force use of ->create rather than ->populate.
- Fixed a bug in the test suite that would fail on certain JSON parsers
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
pkgsrc changes:
- Adjusting dependencies
Upstream changes:
1.001009
- Force operations to work inside a transaction so with_deferred_fks actually works.
1.001008
- Man, I should test better.
1.001007
- Should use Schema->source(), not ->resultset().
1.001006
- Schema->resultset() throws an exception, not return undef, when it can't find
a moniker.
1.001005
- Fixed problem where rules containing an override of has_many weren't applied
correctly.
1.001004
- Fixed problem where descending a has_many to something with two belongs_to
relationships wouldn't get the second belongs_to.
- Updating package for p5 module DBIx::Class::Fixtures from 1.001002
to 1.001003
- Adjusting dependencies according to META.yml
Upstream changes:
- Fix t/var/configs/*.json to use valid JSON syntax
- Fixed DateTime::Format dependencies
- Updating package for p5 module DBIx::Class::Fixtures from 1.001001
to 1.001002
- Adding perl license as license
- Adjust dependencies according to META.yml
Upstream changes:
1.001002
- Allow passing schema object to ->populate
- Check that fixture population dir was created
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
NetBSD Packages Collection.
The Perl 5 module DBIx::Class::Fixtures allows to dump fixtures
from source database to filesystem then import to another database
(with same schema) at any time. Use as a constant dataset for
running tests against or for populating development databases when
impractical to use production clones. Describe fixture set using
relations and conditions based on your DBIx::Class schema.
