| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Jean-Luc Lachance <jllachan(at)nsd(dot)ca>, "Michael S(dot) Tibbetts" <mtibbetts(at)head-cfa(dot)cfa(dot)harvard(dot)edu>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: min() and NaN |
| Date: | 2003-07-24 18:35:46 |
| Message-ID: | 87u19bojr1.fsf@stark.dyndns.tv |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> NULL can be special, because it acts specially in comparisons anyway.
> But NaN is just a value of the datatype.
Does postgres intend to support all the different types of NaN? Does you
intend to have +Inf and -Inf and underflow detection and all the other goodies
you actually need to make it useful?
If not it seems more useful to just use the handy unknown-value thing SQL
already has and turn NaN into a NULL.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-24 18:44:10 | Re: min() and NaN |
| Previous Message | scott.marlowe | 2003-07-24 17:31:54 | Re: PostgreSQL or pl/psSQL equivalent to MS SQL Server's |