From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200105091753.f49Hrsg15378@candle.pha.pa.us>
Subject: libpq++ FieldSize fix
To: jtv@cistron-office.nl
Date: Wed, 9 May 2001 13:53:53 -0400 (EDT)
CC: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

> > Here's a version of my suggested diffs transplanted to 7.1 beta 5.  I'm still
> > looking at the best way to integrate Tom Vijlbrief's fixes (insofar as they're
> > still needed); would 7.2 be a suitable time for incompatible API changes?
> > 
> 
> As far as changes, 7.2 would be fine for changing the API, if there is a
> good reason to do it.  For example, I see getLength returns a short. 
> With 7.1's new longer tuples, that should now be changed to int, at
> least.  (I have updated libpq++/TODO to mention this.)

I was wrong.  It was not getLength, but FieldSize that was the problem.

OK, I thought, how hard can it be to change, and indeed, it was quite
easy.  Patch applied.  Seems we have to break the API to allow long
field values.  Max field length is now 1GB.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026