On Tue, May 13, 2014 at 2:51 PM, David G Johnston
<david.g.johnston@gmail.com> wrote:
> The error is more typical of someone creating a database with UTF-8 encoding
> but then tries storing Latin-1 (or some other) encoded data.
I didn't say that it was the only problem. Just that I had noticed
that other people were using standard_conforming_strings = off when
running DBT2, on the couple of occasions were I looked through a
result set. The fact that this may have accidentally worked before,
when that was the default does not imply that it was ever correct, but
it may at least be possible to get it to work at least as well as it
ever did by doing that. DBT2 doesn't seem to have anything to say
about encoding one way or the other. As I said, it has many problems.
Another thing that I noticed that I didn't like was that it uses the C
locale.
--
Peter Geoghegan