Re: trouble caused by change in 7.3 handling of '' in

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Larry Rosenman <ler(at)lerctr(dot)org>, Vivek Khera <khera(at)kcilink(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: trouble caused by change in 7.3 handling of '' in
Date: 2002-12-19 17:42:15
Message-ID: 200212191742.gBJHgFM23310@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Larry Rosenman <ler(at)lerctr(dot)org> writes:
> > The issue isn't whether the app is broken or not, (it is), but the
> > fact that we ****CHANGED**** behavior with ****NO**** notice
>
> There was notice, to them as were paying attention (eg, anyone who tried
> a beta release). More to the point, I can name half a dozen other
> incompatible changes in 7.3 (most, but not all, forced by schema
> support) that will undoubtedly break some apps. We cannot have a
> transition plan and backwards-compatibility kluge for every little
> compatibility issue, or our progress will grind to a standstill.

That is a good point. Though we knew about the atoi '' potential
incompatibility, there are certainly others, some of which we weren't
even aware of. (We just got SSL fixed in 7.3.1.) So, while we can do
GUC params for some of the big changes, we still aren't going to be able
to hit them all.

> According to the start of this thread, RT's author has recommended that
> RT users stick to PG 7.2 until he can fix the app. That seems a
> perfectly sensible answer to me.

I have a patch I will post now.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-12-19 17:44:59 Re: Table Timemachine!
Previous Message Tom Lane 2002-12-19 17:38:51 Re: trouble caused by change in 7.3 handling of '' in