PostgreSQL 8.0.0rc2 Documentation | ||||
---|---|---|---|---|
Prev | Fast Backward | Fast Forward | Next |
PostgreSQL is a complex software project, and managing it is difficult. We have found that many enhancements to PostgreSQL can be more efficiently developed independently of the main project. They can have their own developer teams, email lists, their own bug tracking, and their own release schedule. While their independence makes development easier, it makes user's jobs harder. They have to hunt around looking for database enhancements to meet their needs. This section outlines some of the more popular externally developed enhancements and guides you on how to find them.
PostgreSQL includes very few interfaces with the base distribution. libpq is packaged because it is the primary C interface and many other interfaces are built on top of it. ecpg is packaged because it is tied to the server-side grammar so is very dependent on the database version. All the other interfaces are independent projects and must be installed separately.
To use other interfaces, you have to do some searching. For example, GBorg at http://gborg.postgresql.org has over thirty interfaces listed in its Drivers/Interfaces section. Some of the more popular interfaces are:
This is the most common interface for Windows applications.
.Net interface for more recent Windows applications.
An older C++ interface.
A newer C++ interface.
A Perl interface with an API similar to libpq.
A Perl interface that uses the DBD-standard API.
The original version of the TCL interface.
A Python interface library.
A JDBC interface.
A newer version of the TCL interface.
That section also contains several server-side languages that are separate projects. pgFoundry at http://pgfoundry.org contains even more projects. Other projects are not even hosted on these servers and you will have to do an Internet search to find them.