Re: Bizarre 7.3.2 bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Larry Rosenman <ler(at)lerctr(dot)org>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bizarre 7.3.2 bug
Date: 2003-04-22 06:09:51
Message-ID: 816.1050991791@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sean Chittenden <sean(at)chittenden(dot)org> writes:
> 3) Add an upgrading note in the 7.4 release notes to the extent of
> ''::INT is now an error and code must be fixed accordingly.

How exactly would this differ from the statement already prominently
made in the 7.3 release notes?

An empty string (<literal>''</literal>) is no longer allowed as
the input into an integer field. Formerly, it was silently
interpreted as 0.

I'm not sure that giving a warning for one release cycle would really
reduce the pain all that much. There are way too many client-side
setups in which notices and warnings disappear into the bit-bucket.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sean Chittenden 2003-04-22 06:20:29 Re: Bizarre 7.3.2 bug
Previous Message Sean Chittenden 2003-04-22 06:01:10 Re: Bizarre 7.3.2 bug