| 1 |
Source: libdbix-introspector-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: gregor herrmann <[email protected]> |
| 4 |
Section: perl |
| 5 |
Testsuite: autopkgtest-pkg-perl |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13) |
| 8 |
Build-Depends-Indep: libdbd-sqlite3-perl, |
| 9 |
libdbi-perl, |
| 10 |
libmoo-perl, |
| 11 |
libtest-fatal-perl, |
| 12 |
libtest-roo-perl, |
| 13 |
perl | libtest-simple-perl, |
| 14 |
perl |
| 15 |
Standards-Version: 3.9.6 |
| 16 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbix-introspector-perl |
| 17 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbix-introspector-perl.git |
| 18 |
Homepage: https://metacpan.org/release/DBIx-Introspector |
| 19 |
|
| 20 |
Package: libdbix-introspector-perl |
| 21 |
Architecture: all |
| 22 |
Depends: ${misc:Depends}, |
| 23 |
${perl:Depends}, |
| 24 |
libdbi-perl, |
| 25 |
libmoo-perl |
| 26 |
Description: module to detect what database code is connected to |
| 27 |
DBIx::Introspector is a module factored out of the DBIx::Class database |
| 28 |
detection code. Most code that needs to detect which database it is connected |
| 29 |
to assumes that there is a one-to-one mapping from database drivers to |
| 30 |
database engines. Unfortunately reality is rarely that simple. For instance, |
| 31 |
DBD::ODBC is typically used to connect to SQL Server, but ODBC can be used to |
| 32 |
connect to PostgreSQL, MySQL, and Oracle. Additionally, while ODBC is the |
| 33 |
most common way to connect to SQL Server, it is not the only option, as |
| 34 |
DBD::ADO can also be used. |
| 35 |
. |
| 36 |
DBIx::Introspector can correctly detect which database you are connected to, |
| 37 |
because it was factored out of a complex, working codebase. On top of that it |
| 38 |
has been written to be very extensible. So if you needed to detect which |
| 39 |
version of your given database you are connected to that would not be |
| 40 |
difficult. |