Linux workstation

Upstream software project

libapache-dbi-perl

Initiate a persistent database connection

About libapache-dbi-perl

Initiate a persistent database connection

This project links 7 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 2 package records; Fedora 44: 2 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.libapache-dbi-perl: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 432 recordsFedora 442 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libapache-dbi-perl
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-tumbleweed
License expression
Artistic-1.0 OR GPL-1.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This module initiates a persistent database connection. The database access uses Perl's DBI. For supported DBI drivers see: http://dbi.perl.org/ When loading the DBI module (do not confuse this with the Apache::DBI module) it checks if the environment variable 'MOD_PERL' has been set and if the module Apache::DBI has been loaded. In this case every connect request will be forwarded to the Apache::DBI module. This checks if a database handle from a previous connect request is already stored and if this handle is still valid using the ping method. If these two conditions are fulfilled it just returns the database handle. The parameters defining the connection have to be exactly the same, including the connect attributes! If there is no appropriate database handle or if the ping method fails, a new connection is established and the handle is stored for later re-use. There is no need to remove the disconnect statements from your code. They won't do anything because the Apache::DBI module overloads the disconnect method.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. libapache-dbi-perl

    Debian 12 (Bookworm) / perl

    1.12-3

    interface connecting Apache server to database via perl's DBI

    allbookworm

Debian 13 (Trixie)

  1. libapache-dbi-perl

    Debian 13 (Trixie) / perl

    1.12-3

    interface connecting Apache server to database via perl's DBI

    alltrixie

Fedora 43

  1. perl-Apache-AuthDBI

    Fedora 43 / Unspecified / source perl-Apache-DBI

    1.12-36.fc43

    Authentication and Authorization via Perl's DBI

    noarch43
  2. perl-Apache-DBI

    Fedora 43 / Unspecified / source perl-Apache-DBI

    1.12-36.fc43

    Persistent database connections with Apache/mod_perl

    noarch43

Fedora 44

  1. perl-Apache-AuthDBI

    Fedora 44 / Unspecified / source perl-Apache-DBI

    1.12-37.fc44

    Authentication and Authorization via Perl's DBI

    noarch44
  2. perl-Apache-DBI

    Fedora 44 / Unspecified / source perl-Apache-DBI

    1.12-37.fc44

    Persistent database connections with Apache/mod_perl

    noarch44

openSUSE Tumbleweed

  1. perl-Apache-DBI

    openSUSE Tumbleweed / Unspecified / source perl-Apache-DBI

    1.120.0-1.5

    Initiate a persistent database connection

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.