Chapter 6. Library and Interface Versions

Table of Contents
6.1. Package and library versions
6.2. libdbi and libdbi-drivers versions
6.3. Determining the library version at runtime

Libraries are no static entities, just as any other piece of software. Some parts evolve, some optimizations are made, new features are requested, and old features may be too cumbersome to support if no one uses them anyway. Any of these developments may result in a new release. This chapter briefly discusses the issues related to library and driver versions.

The version issues with libdbi are a little more convoluted than with a run-of-the-mill library because we have to consider two application interfaces (APIs):

DBI API

This is, as with any other library, the data structures and the functions that you, as a programmer of a software linked against libdbi, need to know about.

DBD API

This is the interface that matters to the authors of database engine drivers.

Both interfaces may change independently, and both may affect the version number of the package as will be discussed shortly.