libpqxx

libpqxx:6.4

  1. Git
  2. lp:libpqxx
  3. 6.4
Last commit made on 2021-12-16
Get this branch:
git clone -b 6.4 https://git.launchpad.net/libpqxx

Branch merges

Branch information

Name:
6.4
Repository:
lp:libpqxx

Recent commits

77c019b... by Jeroen T. Vermeulen

Don't configure on autogen.

8a6f0e3... by Jeroen T. Vermeulen

Regenerate build files.

f1f7f7c... by Jeroen T. Vermeulen

Prepare for 6.4.9.

d631e84... by Jeroen T. Vermeulen

Activate transaction on prepared statement.

Prior to 7.0, libpqxx transactions (including subtransactions)
"activate" lazily. This means that any `BEGIN` statement needed only
executes when you actually start using the transaction.

However, it looks as if prepared statements failed to trigger this.

17ac133... by Jeroen T. Vermeulen

Bump to 6.4.8.

4832014... by Jeroen T. Vermeulen

Hopefully fix an unexported function.

The `extract_value` helper has two specialisations. One was meant to be
inline, the other lives in the translation unit. We recently exported
the latter, but the former needed an `inline` as well.

bf702fc... by Jeroen T. Vermeulen

Fix lint script.

ff7bf80... by Jeroen T. Vermeulen

Fix link error. Backported from 7.0.

Fixes #340.

A missing `PQXX_LIBEXPORT` could cause link errors for a missing
`extract_value` specialisation for `nullptr_t`, when building libpqxx as
a shared library.

b20d2f1... by Tom Lankhorst

Fix handling of eof() in streambuffer underflow.

@tomlankhorst has identified a serious bug which affected the
`ilostream` class. If you opened a large object _as an ilostream,_
and it contained a byte with value `0xff` _at a buffer boundary,_
on a system where `char` is a signed type (such as x86-compatible
systems), then reading of the large object would **mistake the
`0xff` byte for end-of-file** and stop reading prematurely.

d15839e... by Jeroen T. Vermeulen

Regenerate for 6.4 release branch.

Thanks @rkubes for noticing that I hadn't done this.