How to Install and Uninstall libdbix-introspector-perl Package on Ubuntu 16.04 LTS (Xenial Xerus)
Last updated: November 22,2024
1. Install "libdbix-introspector-perl" package
Please follow the guidance below to install libdbix-introspector-perl on Ubuntu 16.04 LTS (Xenial Xerus)
$
sudo apt update
Copied
$
sudo apt install
libdbix-introspector-perl
Copied
2. Uninstall "libdbix-introspector-perl" package
In this section, we are going to explain the necessary steps to uninstall libdbix-introspector-perl on Ubuntu 16.04 LTS (Xenial Xerus):
$
sudo apt remove
libdbix-introspector-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libdbix-introspector-perl package on Ubuntu 16.04 LTS (Xenial Xerus)
Package: libdbix-introspector-perl
Priority: optional
Section: universe/perl
Installed-Size: 46
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Architecture: all
Version: 0.001005-1
Depends: perl, libdbi-perl (>= 1.628), libmoo-perl (>= 1.003001)
Filename: pool/universe/libd/libdbix-introspector-perl/libdbix-introspector-perl_0.001005-1_all.deb
Size: 17116
MD5sum: 3c967160c51734364373063e4038880b
SHA1: 3ad5ea49911863ba7c41a62d41736e72310b307a
SHA256: 367f25e6be4012282212653a4b762da21f3e6114e301320b43baa1b1a998e7f7
Description-en: 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.
Description-md5: bd33bf154dfa77dd2ef7b66666900583
Homepage: https://metacpan.org/release/DBIx-Introspector
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Priority: optional
Section: universe/perl
Installed-Size: 46
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Architecture: all
Version: 0.001005-1
Depends: perl, libdbi-perl (>= 1.628), libmoo-perl (>= 1.003001)
Filename: pool/universe/libd/libdbix-introspector-perl/libdbix-introspector-perl_0.001005-1_all.deb
Size: 17116
MD5sum: 3c967160c51734364373063e4038880b
SHA1: 3ad5ea49911863ba7c41a62d41736e72310b307a
SHA256: 367f25e6be4012282212653a4b762da21f3e6114e301320b43baa1b1a998e7f7
Description-en: 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.
Description-md5: bd33bf154dfa77dd2ef7b66666900583
Homepage: https://metacpan.org/release/DBIx-Introspector
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu