wiki:WikiStart

Version 65 (modified by jtv, 12 years ago) (diff)

--

Welcome! libpqxx is the official C++ client API for PostgreSQL, the enterprise-strength open-source database software. (If "PostgreSQL" is too verbose, call it by its shorter name, postgres).

If you are writing software in C++ that needs to access databases managed by postgres--on just about any platform--libpqxx is the library you use. The source code is available from here, although in most cases you'd normally work with pre-built binary packages provided by a package maintainer for your specific platform, and distributed through your normal package management infrastructure.

For those who arrived at this page through http://pqxx.tk/: that domain name may disappear at some point in the future. Please use http://pqxx.org/ instead, or bookmark this page.

2007-02-01 2.6.9 released

It's finally here: libpqxx 2.6.9. Many things have changed. Bugs have been fixed, new features have been introduced. But most importantly, we're really retiring the old 1.x-style libpqxx API now. This API (where upper-case letters were still used in function names and such) has been supported for more than three years in the interest of backwards compatibility, but has been marked as obsolete all this time.

If you still use any identifiers from the pqxx namespace that have capital letters in them, please replace them with their more modern equivalents. If you use the transactor framework, be especially careful to replace any definitions of OnCommit(), OnDoubt(), and OnAbort(). There will be no warnings or errors if you forget to update these three, so search your code for them to be sure!

Finding Everything

Where What
Sales Pitch Why this library should interest you
Using This Site The various services offered by this development site
Download Page Source archives (no binaries; those depend on your individual platform)
FAQ Frequently Asked Questions, and their answers
Online Documentation Wiki and copies of packaged documentation
Packagers Page Information for maintainers of libpqxx packages
Bug Tracker Known bugs and requests (as in View Tickets option in top button bar)
Bugs by Milestone Bugs and feature requests, but ordered by milestone
Reporting Bugs How to report a problem or request a new feature
Mailing Lists libpqxx-general and libpqxx-announce (Still hosted on the old libpqxx site)
Other Projects Other open-source development projects hosted on thaiopensource.org
Old Site Old home page for libpqxx development (now used only for the mailing lists)
Author and Contributors Who made all this?

For issues not suitable for the mailing list or bug tickets, contact the author at jtv@xs4all.nl.

Also, you may want to have a look at the other open source projects hosted on this site.

Technical Overview

This library works on top of the C-level API library, libpq. You will need libpq in order to use libpqxx.

The first thing you're likely to notice in programming with libpqxx is that unlike other libraries, it revolves entirely around transactions. Transactions are a central concept in database management systems, but they are widely underappreciated among application developers. Another well-known open source database system, MySQL, never even got around to implementing them at all in their own engine, relying on a third-party replacement engine (now owned by Oracle) to provide this functionality instead.

It may sometimes be possible to build limited applications reliably without serious use of transactions. More usually, however, applications are designed without transactions simply because the developers aren't aware of the risks they are taking, and any data loss is rare or small enough not to be noticed. That kind of design was not considered acceptable for libpqxx.

With conventional database APIs, you issue commands and queries to a database session or connection, and optionally create the occasional transaction. In libpqxx you start a transaction inside the connection first, do your SQL work using that transaction, then commit the transaction when it's complete. There are several types of transactions with various "quality of service" properties; if you don't really want to use transactions at all, one of the available transaction types is called nontransaction. This transaction type provides classic, nontransactional behaviour.

Every command or query issues a result object, which is really a smart pointer so it can be copied around without incurring much cost in terms of performance. No need to write special code to check these for success; error conditions are converted to regular C++ exceptions. Result objects can be kept around for as long as they are needed, completely separate from the connections and transactions that originated them.


GTF Contributor