[rt-users] incompatibility with Postgres 7.3

[Jesse Vincent]

Can you send a _specific_ bug report in, then? I was fairly sure that
all of the atoi stuff had been dealt with in the 2.1.x series.


On Thu, Feb 20, 2003 at 06:32:02PM +0100, Louis-David Mitterrand wrote:
> On Thu, Feb 20, 2003 at 12:29:08PM -0500, Jesse Vincent wrote:
> > On Thu, Feb 20, 2003 at 10:44:11AM -0500, Julian C. Dunn wrote:
> > > On Thu, 2003-02-20 at 09:04, Louis-David Mitterrand wrote:
> > > > I just installed RT on our debian (unstable) server and think I came
> > > > accross a bug triggered by a change in the way Postgres 7.3 handles
> > > > integer comparisons: you can no longer INSERT or equate an INTEGER to an
> > > > empty space. In 7.2 the empty space would be silently treated as 0, now
> > > > it triggers this error:
> > > > 
> > > > auction=# select 0 = '';
> > > > ERROR:  pg_atoi: zero-length string
> > > 
> > > Yes, I came across this about two weeks ago. I believe someone replied
> > > and said to me that Jesse's only supporting Postgres 7.2.
> > 
> > Have a look at the current RT 2.1 snapshots. 2.1 (Which will become 3.0)
> > is built to support Postgres 7.3
> 
> But I am using 2.1.75 already.
> 
> -- 
> ldm at apartia.org

-- 
http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.