DBIx-DBH 1.0
- Released by
- TBONE
- Version
- Release Date
- 2011-07-06
- Kwalitee
- 129.03
- Core Kwalitee
- 90.32
- LINKS
DBIx-DBH 1.0 Latest
Kwalitee Issues
- meta_yml_conforms_to_known_spec
-
Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.
Error: Missing mandatory field, 'abstract' (abstract) [Validation: 1.4];value is an undefined string (abstract) [Validation: 1.4]
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: *** ERROR: You forgot a '=back' before '=head3' at line 204 in file DBIx-DBH-1.0/lib/DBIx/DBH/Legacy.pm *** ERROR: =back without =over at line 285 in file DBIx-DBH-1.0/lib/DBIx/DBH/Legacy.pm *** ERROR: You forgot a '=back' before '=head1' at line 339 in file DBIx-DBH-1.0/lib/DBIx/DBH/Legacy.pm
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: DBIx::DBH::Pg, DBIx::DBH::SQLite, DBIx::DBH::Sybase, DBIx::DBH::mysql
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.2,1.0
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: DBIx::DBH::Pg, DBIx::DBH::SQLite, DBIx::DBH::Sybase, DBIx::DBH::mysql
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
Modules
| Name | Abstract | Version | View |
|---|---|---|---|
| DBIx::DBH | helper for DBI connection( data)? | 1.0 | metacpan |
| DBIx::DBH::Legacy | legacy helper for DBI connection data (form dsn, etc) | 0.2 | metacpan |
| DBIx::DBH::Pg | Pg DBI database handle connection specifics. | metacpan | |
| DBIx::DBH::SQLite | SQLite DBI database handle connection specifics. | metacpan | |
| DBIx::DBH::Sybase | Sybase DBI database handle connection specifics. | metacpan | |
| DBIx::DBH::mysql | mysql DBI database handle connection specifics. | metacpan |