Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] float4 confused as int??

From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pghackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] float4 confused as int??
Date: 2000-01-31 18:37:44
Message-ID: 3895D678.A55E96B1@austin.rr.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Ed Loehr wrote:
> 
> Ed Loehr wrote:
> >
> > Tom Lane wrote:
> > >
> > > Ed Loehr <eloehr(at)austin(dot)rr(dot)com> writes:
> > > > emsdb=>   UPDATE contract_activity_type SET duration = 3.5, updater_id
> > > > = 1, last_update = now() WHERE id = 72;
> > > > ERROR:  pg_atoi: error in "3.5": can't parse ".5"
> > >
> > > ?? What version are you running?  I can't reproduce that with either
> > > 6.5.3 or current sources.
> >
> > 6.5.2
> 
> This happens only via DBI/DBD::Pg.  I can't reproduce via psql.

Not getting enough sleep...

Correction:  DBI or not makes no difference.  I can reproduce it on
*this* table via psql, but I cannot reproduce on a newly created table
with a float column.

In response to

pgsql-hackers by date

Next:From: Patrick WelcheDate: 2000-01-31 19:13:56
Subject: Re: [HACKERS] Another nasty cache problem
Previous:From: Don BaccusDate: 2000-01-31 17:45:58
Subject: Re: [HACKERS] END/ABORT

pgsql-general by date

Next:From: Marc TardifDate: 2000-01-31 18:43:17
Subject: automatic timestamp
Previous:From: Ed LoehrDate: 2000-01-31 16:32:55
Subject: Re: [HACKERS] float4 confused as int??

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group