Source: libdbix-introspector-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 13)
Build-Depends-Indep: libdbd-sqlite3-perl,
                     libdbi-perl,
                     libmoo-perl,
                     libtest-fatal-perl,
                     libtest-roo-perl,
                     perl | libtest-simple-perl,
                     perl
Standards-Version: 3.9.6
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbix-introspector-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbix-introspector-perl.git
Homepage: https://metacpan.org/release/DBIx-Introspector

Package: libdbix-introspector-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libdbi-perl,
         libmoo-perl
Description: module to detect what database code is connected to
 DBIx::Introspector is a module factored out of the DBIx::Class database
 detection code. Most code that needs to detect which database it is connected
 to assumes that there is a one-to-one mapping from database drivers to
 database engines. Unfortunately reality is rarely that simple. For instance,
 DBD::ODBC is typically used to connect to SQL Server, but ODBC can be used to
 connect to PostgreSQL, MySQL, and Oracle. Additionally, while ODBC is the
 most common way to connect to SQL Server, it is not the only option, as
 DBD::ADO can also be used.
 .
 DBIx::Introspector can correctly detect which database you are connected to,
 because it was factored out of a complex, working codebase. On top of that it
 has been written to be very extensible. So if you needed to detect which
 version of your given database you are connected to that would not be
 difficult.