Re: varchar truncation from 7.1 to 7.2

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
Cc: terry(at)greatgulfhomes(dot)com, "'ljb'" <lbayuk(at)mindspring(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: varchar truncation from 7.1 to 7.2
Date: 2002-08-03 15:38:20
Message-ID: 200208031538.g73FcLK02596@candle.pha.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Neil Conway wrote:
> On Fri, Aug 02, 2002 at 10:04:56PM -0400, terry(at)greatgulfhomes(dot)com wrote:
> > I agree, I had the same last minute scramble to make apps work with the no
> > longer silent truncation.
>
> I think one area that could be improved is a clear listing of
> client-visible incompatibilities in the release notes (AFAIK we might
> have a 1-line 'Raise error on long varchar' line in HISTORY, but not
> a lot more than that).

I see in 7.2 history:

CHAR(), VARCHAR() now reject strings that are too long (Peter E)

It should have been in the incompatibilities section at the top, though.

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Sanjeev Rathore 2002-08-03 16:13:26 where is OID data stored?
Previous Message snpe 2002-08-03 14:55:21 CVS problem