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

Re: Re: [GENERAL] +/- Inf for float8's

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Re: [GENERAL] +/- Inf for float8's
Date: 2001-06-05 03:07:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> >       -infinity < normal values < infinity < NaN < NULL
> I was thinking about making NaN equivalent to NULL.  That would give
> consistency in ordering, and probably also in arithmetic.  Additionally,
> if the platform supports it we ought to make the Invalid Operation FP
> exception (which yields NaN) configurable:  either get NULL or get an
> error.

I'd like to see the distinction between NaN and NULL retained, since the
two "values" arise from different circumstances and under different
conditions. If a particular app needs them to be equivalent, then that
is easy enough to do with SQL or triggers.

                       - Thomas

On a modestly related note, I'm come over to the notion that the
date/time value 'current' could be ripped out eventually. Tom, isn't
that the only case for those types which bolluxes up caching of
date/time types?

In response to


pgsql-hackers by date

Next:From: chris.bitmeadDate: 2001-06-05 03:08:58
Subject: Re: Question about inheritance
Previous:From: bpalmerDate: 2001-06-05 02:24:51
Subject: Re: Mirrors not tracking main ftp site?

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