DESCRIPTION

Some of the less-frequently used features of DBIx::Class have external module dependencies on their own. In order not to burden the average user with modules he will never use, these optional dependencies are not included in the base Makefile.PL. Instead an exception with a descriptive message is thrown when a specific feature is missing one or several modules required for its operation. This module is the central holding place for the current list of such dependencies, for DBIx::Class core authors, and DBIx::Class extension authors alike.

CURRENT REQUIREMENT GROUPS

Dependencies are organized in groups and each group can list one or more required modules, with an optional minimum version (or 0 for any version). The group name can be used in the

METHODS

req_group_list

This method should be used by DBIx::Class packagers, to get a hashref of all dependencies keyed by dependency group. Each key (group name) can be supplied to one of the group-specific methods below.

req_list_for

Arguments: $group_name

Return Value: \%list_of_module_version_pairs

This method should be used by DBIx::Class extension authors, to determine the version of modules a specific feature requires in the current version of DBIx::Class. See the "SYNOPSIS" for a real-world example.

req_ok_for

Arguments: $group_name

Return Value: 1|0

Returns true or false depending on whether all modules required by $group_name are present on the system and loadable.

req_missing_for

Arguments: $group_name

Return Value: $error_message_string

Returns a single line string suitable for inclusion in larger error messages. This method would normally be used by DBIx::Class core-module author, to indicate to the user that he needs to install specific modules before he will be able to use a specific feature.

For example if some of the requirements for deploy are not available, the returned string could look like: